yashsingh1/xdaforums huggingface dataset:
[Gen8 Android Development] rottenapple88:
finally I did it!!

I've format the device and reinstalled manually the system and SDE.. then, all it works!

Now i must install the googleApps, but i don't want to waste your time! I'll find the solution by me :)

thx for the help!
[Gen8 Android Development] wilsey:
installed the usb drivers? in device manager does adb device show up?
[Gen8 Android Development] bizcuite:
Look the first page to install it, but have all apps is another story (looks Wisley post, he gives solution to try)

Bizcuite
[Gen8 Android Development] Mavasilisk:
Biz, when can we expect you to upload your new version? With the modified data.img (cache outside data.img).
[Gen8 Android Development] Bingoig11:
I suppose yes because when using Bull, it used to work.

I will double check.
[Gen8 Android Development] bizcuite:
When it will be upload ;)

I would like include more things before another update (like usb sharing).

And it's better to wait many times, because more users report bugs (and bugs can be generated by a fix)

Bizcuite
[Gen8 Android Development] Mavasilisk:
You can also upload some test versions like CM nightlies to test it out on time, not after the whole release is published.
[Gen8 Android Development] joaoalex:
Hi

You can also include in next release one way to change usb mode without a restart.

To get usb work in mode 1 i need to change init.rc and restart. to change between adb and usb guest for pen's and 3g dongle i need to change

this line of init.rc

modprobe musb_hdrc mode_default=2

But work's very well the dongle zte mf626 with this release.

thanks

João
[Gen8 Android Development] bizcuite:
:D do you know how many times it takes to compile cm9 just for a fix to try? Just 1h to 2h with my computer :D

I have just a laptop (t60p) with a dual core 1.6ghz for 64bits and 4go of ram.

Hd is big but 5400tr/min only (sorry i don't know if you don't understand tr/min, it's turn by minutes.)

I cannot made a nightly like cyano. And i haven't the time for this.

It's a personal challenge that i would like share and offer ics on theirs tabs.

To be honest i haven't code since 10 years :eek: but i have good knowledge, learn fastl and have a brain, when i use it ^^

I take all my personal time and work time when i can, to answer you (all users) and fix pb when i can.

Don't dream of superpowerfull ics who kill the death :p

I make all for a stable an usefull ics, it's already a beautiful dream :D

Jao thanks for this tips, i have made a kernel today with mode 2 by default.

I make atm a CM9 with active debug for USB sharing, like the kernel that i have spoke.

It's a good news, because i think to be on the good way, wait and see (and learn for me :) )

Bizcuite
[Gen8 Android Development] Mavasilisk:
Now I see, if it takes long time we have to wait patiently. Anyway its "5400tr/min" is 5400 rpm (rolls per minute). Keep up the good work. I hope that if the cache is in the data.img it will bring more stability.
[Gen8 Android Development] bizcuite:
I will make a experimental version of CM9 nearly, be patient one day or maybe two, with kernel.

I will put on it debug for usb sharing if any guys on forum has an idea, and modification on init.rc.

The compilation is finished, i must create and configure the image

I think that, if anybody can see this, bluetooth can be fix by init.rc configuration.

Bizcuite
[Gen8 Android Development] ArcSmurf:
Biz, is your github upto date as would be happy to get my linux partiton back up and running(as it died several months ago) and get it to a state where I can compile(I used to get the latest CM7 updates and build my own image) - may finally be the push I need to get round to understanding the android platform as am a .Net coder for my sins -)
[Gen8 Android Development] Guanfy:
Ok Biz, I've got two logs for you. One is a bootlog using the latest ADB. Surprisingly it did not crash after the boot sequence so I was able to do some screen testing that way. It did eventually stop logging and I switched to the second log from android terminal.

What I found was that if you turn the screen on and off fairly quickly, there is no issue. However, if you leave the screen off for several minutes, it will cause a hard crash and a reboot. Logs are attached below.
[Gen8 Android Development] divx118:
Just in case you didn't know already.

If you read build-system.html in build/core from your source you will find some usefull tips to speed up building. You can rebuild just a single Android.mk file. Also if you change some source look at the Android.mk to see what lib it builds and only adb push that lib to your image and reboot. No need to copy your entire image again.

for example: Changing a file in frameworks/base/services/surfaceflinger Looking at Android.mk in that folder shows that it builds LOCAL_MODULE:= libsurfaceflinger. So you push "adb push ./out/target/product/gen8/system/lib/libsurfaceflinger.so /system/lib" then "adb shell reboot"

I agree with you releasing nightlies has no sense. It only is usefull when there are more devs involved, else it will only slow you down.

divx118
[Gen8 Android Development] bizcuite:
Thanks divx,

I have read a little build-system.html, but not deep, i will read it when the time will be with me. I have just activated cache, i have a good gain (1h for 6-8h to compile entire image with my computer :crying: ).

When i compile, the image is just update with files in relation with the modification in the code. All others files are not remake.

Recompile only framework takes 1h my computer is just slow :D

I have made the experimental version of CM9 with more debug for USB sharing like promise.

Cache is include in data image.

PLEASE:

-takes another new one data_ICS.img (WIPE and save your old data image)

-I have include bootanimation service in init.rc, report if you have a crash

-Add lib for USB test (init.rc modify too in consequence) - you can load driver to test and see the debug (plug - unplug the cable to have debug with a logcat running)

-report if you have a problem

-it's experimental, i will make later (few days) another version with all add-on in experimental version, but clean.

A70S and others 800x480 (DPI 120 by default):http://www.mediafire.com/?h255yzqz9d7yix6

A101 (DPI 120):http://www.mediafire.com/?yjwn6jezuxzl1vu

I made the kernel ATM (compilation in progress), you can use the kernel from first page. I will just add more debug in kernel for USB.

It's experimental, i find tablet more smooth, but the boot is more long.

Bizcuite
[Gen8 Android Development] Guanfy:
I've gotten the new image installed and setup. It does seem to run a bit smoother, but all other problems that I have had with your ROM so far are still there. Still have crashes, market is still no good, along with all other known issues. As far as compiling the ROM goes, if you can tell me how to do it I can help with that. My computer is a 6 core monster running at 3.9Ghz with 16gb 2133Mhz ram, soon to be 32gb. I think I could compile a wee bit faster than you :)
[Gen8 Android Development] bizcuite:
Thanks for this, Guanfy, but i prefer have the computer under my eyes to work and make all i want on it when i want.

I can have monster machine too (i work in visualization system, machines had 40cores and more, and 256Go of Ram ;) like the HP 980G7) but no access out f work :p

For market, have you got a failed install or just app doens't want appear (it's normal)?

The most impact that you can have is with cache, it's transfert to data image.

I must see if others users has same problem.

Bizcuite.
[Gen8 Android Development] Guanfy:
Market installs fine, but once you access it there are no apps to choose from, due to the fingerprint in build.prop not being quite right. That is what I meant by that.
[Gen8 Android Development] bizcuite:
Yes i haven't modify the build.prop again, i wait to finish that i have in progress (fix usb).

Guanfy, your first log is empty in your last attachment :) .

I put in attachment kernel image and driver USB (i think that i have forgotten to put its on image, you must verify if folder /lib/modules_USB)

There are lots of debug activated in kernel for USB(and sound), it's useless for you, but i need it.

At each boot there a "fix permission" service (thanks for Wilsey) I prefer apply it all the time, i had lot of problem with permission on my SGS1

Bizcuite
[Gen8 Android Development] Guanfy:
Grr.. I really need to sanity check my .txt files before I compress and upload them. Anyway, you want me to flash the new zImage, check for the usb driver and then upload the boot logs to you?
[Gen8 Android Development] bizcuite:
No Mavasilisk would like try the new image with cache in data image file, then i have made this kernel and image for users who wants try and debug usb if they can/want.

You can do what you want with the image file. I don't need any log file atm because we have sames problem and same hardware for this.

I will now try another kernel with USB driver update from Gen9 drivers.

USB sharing need lots of update, there are many things has changed since Ginger.

Bizcuite.
[Gen8 Android Development] wilsey:
Hey Bizcuite

Tried the new V1.01, Seems smooth and stable :)

No crashes thus far, Played Some angry birds without a glitch :)

Market Fully working applyin fix a few ages back, Might i recommend setting Build.prop dpi to 160 by default instead of 120 on the A101, No need for any market hacks with that dpi and Display is nice, Save alot of people asking for help lol

Tried the new USB kernel also and pushed modules_USB to system/lib , Windows shows 2 Removable storage devices but they aren't mounted correctly and thus cant be viewed :)

Mounting USB in repair screen i see kernellog.txt, i attached it for your viewing pleasure :D

Also add a LINK to a nice script that lets you set partitions and move system folders to a second internal partition as sd-ext etc
[Gen8 Android Development] bizcuite:
For USB sharing, i must update kernel to have MTP or other share method.

I try to fix errors and compile it.

I will share modules when it will be ok to try.

I see only one drive under windows (cannot mount it too), have you make any modification on init.rc to load drivers?

Bizcuite
[Gen8 Android Development] wilsey:
I have a separate swap partition, it might see that as a removable device, I have not yet edited init.rc no

Shall await your fixes :)
[Gen8 Android Development] Mavasilisk:
It seems to lag a bit, I will try to put the old kernel and report later. Market works you just have to set it up.

EDIT: I deleted the trash apps which come pre-installed and its lightning fast now. As soon as the device boots and the unlock screen comes up the device is completely useful without the fresh start slowness. Gonna test more and report later.
[Gen8 Android Development] bizcuite:
Which files do you speak about?

Can make me a list please?

Thanks.

Bizcuite
[Gen8 Android Development] Mavasilisk:
I meant I deleted build-in apps in system/apps which doesn't make much sense but it loads faster at beginning. Anyway, it stil crashes.

EDIT: Like Phone.apk , Calendar.apk ... everything that isnt useful (calendar is but it was an example)
[Gen8 Android Development] bizcuite:
ok, i have seen a pb.

I have activate a debug for mmc, if you make a logcat , you will see lots of debug about mmc.

The tab is slow for this reason.

I will make another kernel to fix this or take kernel on first page

Bizcuite.
[Gen8 Android Development] Mavasilisk:
You mean kernel V1.01 has mmc debug or V1.01 experimental ?
[Gen8 Android Development] wilsey:
Bizcuite

Here is a working Fix for rotation on start up/App loading, Works perfect an the A101

In init.rc edit : Put N instead of Y here.

# Disable rotation of touchscreen and sensor for 101

write /sys/module/hid_hanvon/parameters/rotate180 N

write /sys/module/mma7660fc/parameters/rotate180 N

In Build.prop add this line anywhere :

ro.sf.hwrotation=180

Screen is rotated corectly on start up and also apps load proper rotation :)
[Gen8 Android Development] bizcuite:
It's activated on experimental only. :)

Thanks, i will see if i can use it, but the result is same.

Just the way is different, by line changed in init.rc, you pass by kernel way, and other you pass by system. (i don't know if there is a difference about resources used between the two ways, if yes i think kernel way is better)

Bizcuite
[Gen8 Android Development] wilsey:
With the way it is now, On A101 at least, The screen starts upside down, But will flip when held for a second in correct position, Apps However start with wrong rotation

With the way I posted screen starts in correct position , And Apps also load correctly :)

setprop ro.sf.hwrotation 180 in init.rc does same thing. As am sure you know.

Maybe you can find better way with kernel :)

This Tab is gettin better Daily, Thanks :)
[Gen8 Android Development] Mavasilisk:
It works way faster with V1.01 kernel (1st page). No slowness. The only major bug for now is the force close which is almost fixed now.
[Gen8 Android Development] bizcuite:
Ok, thanks for your report.

To all: used kernel on first page with experimental cm9.

FYI: I try to update usb driver from gen9.

Compilation is ok after 2 days of work but it doesn't want to boot, i will try to compile drivers like module and see if mtp or usb mass storage works.

Bizcuite
[Gen8 Android Development] Mavasilisk:
After a while playing around it seems like the device freezes and reboots when I open an app which makes the device think a lot. Can an adb log provide the source of this problem or u need a minicom log?

EDIT: Have you ever though that the force closes might be caused by the system itself? You made it for your device and you have 512mb so you took a system that was made for 512mb and we use it too but we have 256mb. Can this cause the crashes?

Example (just in case somebody didnt get what I meant):

Your device has 512MB and the system adresses it. OK

Our devices have 256MB and the system thinks we have 512mb, so after the whole ram (256mb) is used the system doesnt know what to do and just freezes.
[Gen8 Android Development] bizcuite:
Your hardware is defined by "bios". I don't think that your crashes has no relation with this.

Just see if in parameters=>about phone/tablet if you have 200MB (maybe more or less, i have 498 on mine)

Have take new data image?

TO ALL: If anybody has same crashes like Mava. Please report it here :)

Bizcuite
[Gen8 Android Development] Mavasilisk:
Yes. The data image is brand new. Everytime you upload an update I put a new data image. About device > Memory 237 MB. Ok I have no clue for now what is causing this.
[Gen8 Android Development] nimafire:
is there any persian lang for this rom ?
[Gen8 Android Development] Mavasilisk:
Its in alpha stage. There are lots of other major things to fix and I dont think persian is going to be added soon. You can look around how to add it yourself cuz Cyanogenmod is very popular and I'm sure you will find how to do it.
[Gen8 Android Development] ArcSmurf:
Hi Biz, been on hols for a week and not had much time to test but updated this morning to latest kernel but kept my data image overal seems smooth but still experience randpm freezes when starting apps and sometimes these result in the tablet rebooting, other times have to power off.

Will try and get some adb logs when back at work tomorrow to see if can help debug this issue
[Gen8 Android Development] bizcuite:
Try with a clean data image, i think that will be better.

I have too the crash on reboot or power off tab.

Bizcuite
[Gen8 Android Development] Mavasilisk:
About the crash/reboot/power off tab bug can you test it on your tab or we have to send u some logs?
[Gen8 Android Development] bizcuite:
I haven't every time crash reboot/power off. Tab has never crashes when the tab is power on and active.

I can have debug, because i use lot minicom and log all that's happening.

I begin to think that port our kernel to 3.0 is maybe a better way than port 3.0 drivers on 2.6.29. (if anybody can try to begin to port it???, if he has knowledge for it???)

USB driver gives me lots of problems, i fix all errors since 2 days, for each files. There is an enormous work (and archos has made lots errors on pointers :) ).

I think fix all errors tomorrow, and see if it boots (first try was unsuccessful, kernel is load but black screen after).

Bizcuite
[Gen8 Android Development] erdemdengel:
I installed the kernel and initframs

How can I install openaos-cm.img?

its located at the root of the sdcard
[Gen8 Android Development] ArcSmurf:
Place it on the root of the internal memory
[Gen8 Android Development] erdemdengel:
I can not reach my archos internal storage

is it possible from SDE?
[Gen8 Android Development] Mavasilisk:
He meant internal storage. Mouth your pc with USB cable to your PC and the main folder that appears is the place where u have to put the .img files.
[Gen8 Android Development] eymas:
I can confirm that it works well upon an Archos 43, only for the most important problem:

No soft buttons and constant SystemUI crashes.

If this can be fixed then i'd love to aid you in testing on the A43.
[Gen8 Android Development] Guanfy:
If you don't have soft buttons and have the lastest installed image, something is wrong. It was found that adjusting lcd density in build.prop fixed that issue. What device do you have? If you let us know we can make sure you have the right setting to see your tablet layout correctly.
[Gen8 Android Development] eymas:
I've just edited my post stating that my device is the Archos 43. and I do have the latest image(If that is the one in the first post)

And perhaps the LCD Density might fix it of course.

For now I'll see if i can get Button Savior upon it so it's usable.
[Gen8 Android Development] Guanfy:
I'm not sure what the correct setting for the A43 is. Biz or another A43 user might be able to tell you. If you plan to help dev this ROM, it might be helpful to put your device in your signature. That way everyone can quickly see what device you are using, which can help save time in troubleshooting. Good luck on getting your buttons back.
[Gen8 Android Development] bizcuite:
EDIT: Too late :) i read last posts and make an answer :)

EDIT2:

I will wait that you make a test after fix DPI and see if it's better.

I think that if there is pb, i must see the screen format. Maybe it's invert (800x480 become 480x800) and DPI must be configurate with another value.

Bizcuite
[Gen8 Android Development] eymas:
Update 2: 160 DPI, Still no softbuttons. I'll test different ones from time to time. Button savior still works.

...and the touchscreen still works cursor-based...

Update 3: Requested screen config:

heightPixels=854

widthPixels=480

(Gathered from included dev tools>configuration)
[Gen8 Android Development] nikunj87:
Archos 70 IT - ADB output

# pwd

pwd

/sys/devices/platform/ohci-omap.0/usb1/1-2/1-2:1.1/0003:227D:070A.0004

# ls -l

ls -l

total 0

lrwxrwxrwx 1 root root 0 Oct 18 11:03 driver -> ../../../../../../../bus/hid/drivers/hanvon

drwxr-xr-x 2 root root 0 Oct 18 11:03 power

lrwxrwxrwx 1 root root 0 Oct 18 11:03 subsystem -> ../../../../../../../bus/hid

-rw-r--r-- 1 root root 4096 Oct 18 11:03 uevent

# cat uevent

cat uevent

DRIVER=hanvon

HID_ID=0003:0000227D:0000070A

HID_NAME=UNITEC USB Touch (Win7)

HID_PHYS=usb-ohci-omap.0-2/input1

HID_UNIQ=

MODALIAS=hid:b0003v0000227Dp0000070A

Hope this helps.
[Gen8 Android Development] bizcuite:
Thanks a lot!

Just read the previous posts, there is the solution to have the screen with the good orientation.

Just push the init.rc in attachment file by adb.

EDIT: The touchscreen configuration file is already in the rom in /system/usr/idc file Vendor_227d_Product_070a.idc (HID_ID=0003:0000227D:0000070A)

Can you see if touchscreen and screen works well now?? After you have put the new init.rc on A101 tabs

Bizcuite
[Gen8 Android Development] nikunj87:
Sorry if I have misunderstood but I have an Archos 70 8GB IT 7 inch tablet, can i use the same init.rc as well?

Thanks,
[Gen8 Android Development] bizcuite:
Ah sorry, it's just for A101, others tab is not concerned by this init.rc.

Bizcuite
[Gen8 Android Development] Guanfy:
I dug through the old CM7 threads and changed my menu.lst entry to what was posted there. Attached are the logs from the effort.
[Gen8 Android Development] bizcuite:
I must update kernel for your touchscreen, i will need you when i will have time to see driver.

Are you ok, and time to help me (not now, i will pm you when i will be ready)?

I will PM and send you a kernel to try.

I have make lot of tries to have my touchscreen working.

Debug a unknown material is really hard lol

Bizcuite
[Gen8 Android Development] nikunj87:
LOL ... Ok Sure, i will be ok to try out the revised Kernel. Let me know when you're ready. Thanks.
[Gen8 Android Development] Mavasilisk:
Send it to me also, I've got adb up and running and also up for testing.
[Gen8 Android Development] bizcuite:
Looks second post please, there are all, file and how to.

Or just try with command gives by Divx118 (previous page).

Thanks in advanced!!

Bizcuite
[Gen8 Android Development] bizcuite:
For A70S ONLY (not A70S2, Touchscreen works well)

Can you try this kernel if your Touchscreen was not good? (paste in second post too)

Just rename it "zImage", don't uncompress it!!

Thanks for your report of touchscreen

Report like:

With one finger, how reacts the TS

With 2 fingers, how reacts the TS

With a log of 2 situation it will be cool for me :) just copy and paste the log that is interesting (when you touch the screen)

Bizcuite
[Gen8 Android Development] bizcuite:
I cannot find in your log your first error that block the complete boot:

<4>I//system/bin/fsck_msdos( 1321): ** /dev/block/vold/179:1
<4>I//system/bin/fsck_msdos( 1321): Invalid signature in boot block: 0000
<4>I/logwrapper( 1321): /system/bin/fsck_msdos terminated by exit(2)
<4>D/dalvikvm( 1515): GC_CONCURRENT freed 16K, 30% free 12613K/17799K, paused 2ms+123ms
<4>E/Vold ( 1321): Filesystem check failed (not a FAT filesystem)
<4>W/Vold ( 1321): /dev/block/vold/179:1 does not contain a FAT filesystem
<3>NTFS-fs warning (device mmcblk0p1): is_boot_sector_ntfs(): Invalid boot sector checksum.
<3>NTFS-fs error (device mmcblk0p1): read_ntfs_boot_sector(): Primary boot sector is invalid.
<3>NTFS-fs error (device mmcblk0p1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
<3>NTFS-fs error (device mmcblk0p1): ntfs_fill_super(): Not an NTFS volume.
<4>E/Vold ( 1321): /dev/block/vold/179:1 failed to mount via NTFS (Invalid argument)

The boot was finished when you have send me this log....

<4>D/PowerManagerService( 1435): bootCompleted
<4>V/OtaStartupReceiver( 1542): onReceive: intent action=android.intent.action.BOOT_COMPLETED mOtaspMode=-1

I don't know how you had this error, can you reproduce it?

And i don't know what is mount on HDD version.

Bizcuite
[Gen8 Android Development] nikunj87:
Hi Bizcuite,

Thanks for the prompt updates... Just so that I am checking against the right device - can you confirm Archos 70 IT 8 GB = A70S, am I right?