yashsingh1/xdaforums huggingface dataset:
[Gen9 Android Development] trevd:
Hi Folks

I've just given my self a lesson in board bring up on omap arm devices :) and I'm making progress with the A101S board.

It creates the framebuffer in /dev/graphics/ and shows the boot animation although i've still got an issue with surfaceflinger and gralloc and framebuffer not being typewriter when I try to use the pvr drivers. I presume it something to do with the issue below which happens pretty early in the boot.

omapfb_calc_addr:892
Backtrace:
[<c008690c>] (dump_backtrace+0x0/0x138) from [<c0650164>] (dump_stack+0x20/0x24)
r7:c0a4f764 r6:d9b9a000 r5:00000000 r4:d931ce90
[<c0650144>] (dump_stack+0x0/0x24) from [<c0322e6c>] (omapfb_setup_overlay+0x158/0x4b8)
[<c0322d14>] (omapfb_setup_overlay+0x0/0x4b8) from [<c03236a0>] (omapfb_apply_changes+0x4d4/0x5c8)
[<c03231cc>] (omapfb_apply_changes+0x0/0x5c8) from [<c03240f4>] (omapfb_probe+0x960/0xda0)
[<c0323794>] (omapfb_probe+0x0/0xda0) from [<c03624f8>] (platform_drv_probe+0x24/0x28)
[<c03624d4>] (platform_drv_probe+0x0/0x28) from [<c0360f00>] (driver_probe_device+0xdc/0x1c8)
[<c0360e24>] (driver_probe_device+0x0/0x1c8) from [<c0361064>] (__driver_attach+0x78/0x9c)
r6:c087e350 r5:c0872d9c r4:c0872d68 r3:00000000
[<c0360fec>] (__driver_attach+0x0/0x9c) from [<c035fb5c>] (bus_for_each_dev+0x58/0xa0)
r6:c0360fec r5:c087e350 r4:00000000 r3:00000000
[<c035fb04>] (bus_for_each_dev+0x0/0xa0) from [<c0360b14>] (driver_attach+0x2c/0x34)
r6:c0880748 r5:d928d0c0 r4:c087e350
[<c0360ae8>] (driver_attach+0x0/0x34) from [<c0360698>] (bus_add_driver+0x138/0x2d8)
[<c0360560>] (bus_add_driver+0x0/0x2d8) from [<c03616cc>] (driver_register+0xd4/0x160)
[<c03615f8>] (driver_register+0x0/0x160) from [<c03629a0>] (platform_driver_register+0x80/0x9c)
[<c0362920>] (platform_driver_register+0x0/0x9c) from [<c0032644>] (omapfb_init+0x40/0x70)
r5:c004d778 r4:c004d7b0
[<c0032604>] (omapfb_init+0x0/0x70) from [<c007c768>] (do_one_initcall+0xb4/0x1b0)
[<c007c6b4>] (do_one_initcall+0x0/0x1b0) from [<c0008b64>] (kernel_init+0xb0/0x16c)
[<c0008ab4>] (kernel_init+0x0/0x16c) from [<c00d99a8>] (do_exit+0x0/0x6fc)
r6:c00d99a8 r5:c0008ab4 r4:00000000 r3:00000000
data_start_v=0xe2000000
rotation_type=0
cannot apply mgr(lcd) on inactive device
omapfb omapfb: failed to apply dispc config
cannot apply mgr(tv) on inactive device
omapfb omapfb: failed to apply dispc config
cannot apply mgr(lcd2) on inactive device
omapfb omapfb: failed to apply dispc config
omapdss DPI: Could not find exact pixel clock. Requested 68930 kHz, got 68929 kHz
panel_enable [wxga10]

I've got myself a Linaro JellyBean to boot all the way on the new kernel as that allows you to disable hardware rendering on the launcher

I'm just having a look at that firmware myself, some very interesting changes...... /system/lib/modules contains the pvrsrvkm_sgx540_120.ko and omaplfb_sgx540_120.ko, I'm just going to play around with some jellybean builds and see if I can get the drivers playing ball.

I assume if archos have created a new kernel in preparation for a JellyBean Rom on either the G10 or G9 then that would make this work kind of redundant for now?
[Gen9 Android Development] scholbert:
Great work... so you took the Pandaboard files or built your own?

Yeah i also wondered about that.

If you look at the 3.0.21 the known pvr part is missing now.

Guess the whole graphics stuff is changing for new releases, but i'm not a Ducati specialist :p

Might get redundant, but don't forget the education :laugh:

Anyway you always give nice information to the community!

Keep on your great work.

Cheers,

scholbert
[Gen9 Android Development] trevd:
I acquired this book [ Embedded Android ] and decided to started from scratch, I've been using the Blaze and Panda as references.

I've made some major changes to the archos firmware/images which I will document very soon for everyone as I think we can bring the Archos Roms into line with the rest of Android.

I built myself a 3.0.21 kernel this morning and created myself a 4.0.24 rooted firmware ( I presume this number is related to the Gen10 ). The pvr/omaplfb kernel objects do get installed on boot although I still have not located exactly where that is happening. I'm still a little confused by how all this graphics stuff fits together and I seem to be going round in a segfault circle when trying to use the 3.0.21 drivers on a JellyBean Rom. I probably just need to add more method to my madness as I'm probably just repeating things I've already attempted.

I think I may go back to working on the 3.0.31 kernel if I don't make any headway

@Quallenauge : Have you got pvr drivers working on your 3.0.31 Kernel? What Is the "Secret Sauce" I need to Add?

It's certainly an education :) and I think this is worth carrying on with as It it means we can keep the device up to date long after archos has stopped supporting it.

And yourself, Although much of the H/W stuff is over my head at the moment, I'll understand one day :laugh:

Slightly off topic, I was wondering if you had looked into extracting the public keys from Gen10 F/W , It was something I made a naive attempt to do but I got lost in a sea of Hex! :silly:
[Gen9 Android Development] scholbert:
Cool, that's great... that's the way i like.

Interesting book as well. Few year ago i purchased "building embedded linux systems" from O'Reilly.

Good basics here, but little old skool in the meantime :angel:

Back on track... started digging around in the project files of the more open platforms in the meantime,

but unfortunately time is lacking to produce some useful output. So it's great you do!!!

I must admit, i got no clue right now...

Always follow the path of least resistance ;)

... at least first.

That'll be really great achievement.

Thanks alot... but no active hacks for some time now :highfive:

I would extract them, but in fact i'll need a dump of the first blocks of a Gen10 device. Maybe we should ask cajl for help...

You can't extract the keys from the firmware file because you'll need the key first to extract the bootloader out of the firmware file :p

We need to dd if=/dev/block/mmcblk0 of=/mnt/sdcard/first-64k.bin bs=512 count=128 or similar from a real device...

Best regards,

scholbert
[Gen9 Android Development] Quallenauge:
Yes I had the pvr drivers working with the 3.0.31 kernel.

It is really important to use the right combination of pvr driver, omaplfb and omapfb. And it was neccessary to build the pvr driver as module. But I used the initialization routine of android-display.c for the graphics subsystem. Did you look what is at the affected line on the source code? Hint: I use the program addr2line for that. You can use the address as input and gets the source file with line number.

Don't forget the use the binary for the arm architecture of this program. (I sometimes use the wrong binary and wonder about wrong results).
[Gen9 Android Development] trevd:
Ay, I saw you had mentioned about the android-display.c on the e2e.ti.com thread, You also mentioned you pull some files from the blaze tree, any expansion on that? or was the just a bit a developers luck LOL :D

I'll grab myself addr2line and go back to work on 3.0.31 for this evenings session. So far I used a combination of printk and adb to bring up my kernel, I practically had to add the vram/fb device setup code on a line by line basis but after much hackery and a sprinkle of that dev-Luck I mentioned, the board-archos_a101s.c code is as near as damm it, indentical in implementation to what you did with the A80S. :good: :victory:

A couple of things I've noticed, You might want to add FTracing and tracing to the config as, although not include in the CM10 init we used , standard JB builds include an init.trace.rc [ androidxref ] . I supoose Tracing can't hurt with regards debugging etc.

I suppose when you return full we should pool it all together and see what we've got!

Also as an interesting aside, my sister just got a Samsung Galaxy Nexus ( I think my family is addicted to android ) which came with a 4.1.1 rom and to my surprise a 3.0.31 kernel. :)

As a former work colleague and good friend of mine says "LETS DEVELOP!" :)
[Galaxy S II Q&A, Help & Troubleshooting] NoP_Compiler:
Hi.

I bought a Galaxy S2 phone in July and installed CM9 nightly (and now CM9 stable) on it.

Sometimes (5 times in August), when I take the phone from the table or from my pocket and try to switch the screen on, I find that the phone does not respond to the "power" button to bring the screen back on (just black screen). The phone is somewhat hot at this moment and I have to remove the battery to switch it on again.

When I switch it on again, the battery has reduced a lot (too much for the time passed since I left the phone over the table) just like if the phone was stuck in a battery-consuming process, not just "crashed".

This happens even if I'm connected to the charger (the battery goes down).

I'm using CM9 stable and thoravukk kernel ... any idea of what's wrong? Should I check a different kernel? Is a known CM9 problem and is not kernel related? Anyone else suffering the same problem?
[Galaxy S II Q&A, Help & Troubleshooting] oddlyshapedstickman:
Have you tried installing after full wipe?
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
u r experiencing SOD(sleep of death) thats ur phone is not coming back after deep sleep. reason might be due to kernel, try changing the kernel to stock cm9 or siyah kernel and see:)
[Galaxy S II Q&A, Help & Troubleshooting] NoP_Compiler:
Hi.

I installed cm9-nightly-2012-07-28 after a full wipe (previously to this, I was using samsungs' stock 4.0.4), and I had this problem after the full-wipe install...

I passed from the nightly to the stable without the data wipe, and it's still happening...

I'm starting to think on make small tests. First of all, I was planning to replace thoravukk with siyah, to see if it's a kernel problem, or discard the kernel... but wanted to know if anybody is suffering the same problem.

(A friend of mine also suffers it with CM9 and the Galaxy S1...)

Thanks for answering.
[Galaxy S II Q&A, Help & Troubleshooting] NoP_Compiler:
Just a question ... if the phone is "deep sleep" ... why is so hot and why battery drains so much ? :-?

I'll test siyah...

Thanks
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
try siyah v4.1rc1 after installing the same go to recovery wipe cache/dalvik and do fix permissions and then allow a cpl o recharge cycle for the kernel to settle dwn and then see:)
[Galaxy S II Q&A, Help & Troubleshooting] oddlyshapedstickman:
Try a full wipe, wipe cache and delvik and reinstall stable, keep stock CM kernel.

Although you can flash from nightly to stable, its good to do data wipe beforehand since you aren't going to flash anything above stable.
[Galaxy S II Q&A, Help & Troubleshooting] NoP_Compiler:
Hi.

I didn't wipe the data because it was just a couple of weeks between the nightly and the stable, very minor changes and seemt that wiping was not needed (and remember that I was having those "crashes" with the nightly, and I did a complete wipe to install it).

I installed thoravukk because the stock kernel does not have BLN support and I need it because SGS2 does not have a notification led and I miss text and whatsapp messages if I can't heard the audible notification ...
[Galaxy S II Q&A, Help & Troubleshooting] oddlyshapedstickman:
Ahh OK, well you could Siyah as that has BLN.
[Galaxy S II Q&A, Help & Troubleshooting] midnightflash:
So... You are not alone! I've got a I9100 with cm9 too. I've the described error too. Also over the nightlys over the past months it changed a bit to do it while in active use. Loss of 30% or something like at once!

I put the charger in while reboot. But this is no matter.

Also a friend of mine has the same problem with a stock SGS2 with the original 2.3.

Greetings
[Galaxy S II Q&A, Help & Troubleshooting] RusherDude:
The "suddently battery drop" problem is not only related to the Sleep of Death problem described by the OP. It appears in a lot of situations and in mostly all occations (probably including this one), it's just that the battery isn't callibrated anymore and you'd do a battery callibration to prevent those "suddent losses".
[Galaxy S II Q&A, Help & Troubleshooting] sker83:
Calibrate your battery ! 3 charge et tout rentre dans l'ordre.

Envoyé depuis mon GT-I9100 avec Tapatalk
[Galaxy S II Q&A, Help & Troubleshooting] NoP_Compiler:
It's been more than a week since I intalled Siyah kernel 4.1rc1 and the problem has not appeared yet.

Let's cross the fingers and wait for a couple of weeks more and I'll confirm that the problem is with CM9-stock-kernel and thoravukk kernel.

Thanks!
[Galaxy S II Q&A, Help & Troubleshooting] DSF:
I've tried with different versions of Siyah kernel (v4.1.5, v4.0.1) and still got SODs.. Reverted back to stock CM9 kernel and same..

I'm leaving wifi on with "Keep Wi-Fi on during sleep": Only when plugged in.

Strangely, I have found my phone SODed even when plugged in charger (that was only with siyah kernel if i remember right)..
[Galaxy S II Q&A, Help & Troubleshooting] NoP_Compiler:
Never suffered it again since I installed Siyah kernel...

--
[Galaxy S II Q&A, Help & Troubleshooting] cristianu:
black screen

I have the same problem with 7 different stock roms and kernels. can you help me ?
[Galaxy S II Q&A, Help & Troubleshooting] roddem:
the cm10 has an option to take screenshot in the power menu and so does all other ics roms.. but the other jellybean roms like slimbean , rootbox anad ressurection remix jb .. how to take a screenshot in these ?as neither does the home and lock button thing work and nor is there any other option to take

please help
[Galaxy S II Q&A, Help & Troubleshooting] Sun90:
its Volume down + Power button pressed simultaneously for a cpl of sec's to make the screen shot on AOKP based roms, try the same and see:)
[Galaxy S II Q&A, Help & Troubleshooting] oddlyshapedstickman:
Have you tried power key+volume down simultaneously?
[Galaxy S II Q&A, Help & Troubleshooting] roddem:
Thank you so much. ..

New to all this didn't know of this.

Now I can happily flash the jb ROMs :D
[Galaxy S II Q&A, Help & Troubleshooting] roddem:
Works like a charm. Thank you :)
[Member-Found Deals] gears177:
can anyone find any deals on this the lowest ive been able to find is 340 im looking to sell my acer a500 with keyboard case and 500gig harddrive to purchase it?

(wont let me go to the selling or buying threads it says i dont have access O_o)

ive looked on ebay amazon and just googled it

also daily deal on ebay for 8.99$ for a 16gb microsd card with the sdcard and usb adapters

http://www.ebay.com/itm/SanDisk-16G...w-USB-Flash-Card-Reader-Adapter-/271040661563
[Member-Found Deals] SLB9884:
FYI no:)one can understand what you are selling & or asking for
[Member-Found Deals] Solar.Plexus:
Allow me to translate.

OP wants to sell an Acer a500 with keyboard case and 500GB hard drive.

OP wants to buy an Acer w500 for less than $340 (if possible).

OP has found a deal! $8.99 for a 16GB microSD with USB and SD adapters on eBay.
[Galaxy S III Q&A, Help & Troubleshooting] gers1978:
On my iPhone, I could punch in the L2TP settings for the VPN with just a username, password and shared secret.

On Android, it seems to also be asking for a pre-shared key, and it won't let me any further until I put one in. But my VPN provider doesn't say what the PSK should be, and like I said, I never needed to enter it on any other device.

Any idea what's going on?

Thanks
[Desire Q&A, Help & Troubleshooting] MattBooth:
So, I bought another battery. Will this sort it?

Also, what's the usual procedure?

Should I charge the battery to full in the phone (turned off) then boot, set up, then charge again and reset battery stats?
[Desire Q&A, Help & Troubleshooting] Ronok:
The problem is that the battery control chip doesn't take into account that the battery ages.

Resetting battery stats or charging while turned off will only clear the stats you see in the settings menu. This guide will make your battery drain to 0% again: http://xdaforums.com/showthread.php?t=1534892

I don't know what a new battery will do though.
[Desire Q&A, Help & Troubleshooting] MattBooth:
I gathered that, but as the phone is going to a new user (my stepson) we got him a new battery anyway :p

I just wondered what the correct procedure is. I know you need to do a first charge with a new battery, as with a new phone, however, this phone obviously has a working ROM already on it.

So, the phone is charging now, switched off. Should I turn it on, use a little, then use the battery calibration app to delete the stats and then drain to 0%?
[Desire Q&A, Help & Troubleshooting] Ronok:
Well, that assumption is probably inherited from the NiHM batteries in the past, because it's not needed with Li-Ion batteries. In fact charging to 80% is better than charging to 100% and keeping it plugged in.

You can read more about it here and here.

Just charge it and use it for a full cycle. If it shuts down at 15%, you can try the battery calibration from the thread I mentioned above. If it doesn't, you're battery capacity is the same as the one the battery chip has calculated, which is good.
[Desire Q&A, Help & Troubleshooting] MattBooth:
So, why does the first charge take so long?

This thing is still charging and it's been on the charger for 3 hours, whereas usually it'd be charged fully by now.

Been like that for every Li-Ion battery I've ever had (including my S3, took around 6 hours to charge, usually takes 3).

EDIT:

Just to clarify, I don't intend on leaving it past the green light. As soon as it says it's full I'll be taking it off charge and not trying ot overcharge it. But I still have the orange charging light after 3-4 hours.
[Desire Q&A, Help & Troubleshooting] Ronok:
To be honest, I don't know. Maybe it's a safety to prevent overcharging. Coincidentally, I've got exactly the same issue now. I asked about it in the calibration thread. I suppose it's normal, but I'm not sure about that.
[Desire Q&A, Help & Troubleshooting] jmcclue:
my battery took just over 6 hours to charge the other day from completly dead

Sent from my HTC Desire
[Galaxy S II I9100G Android Development] incarnation95:
Another codename android:confused:
[Galaxy S II I9100G Android Development] samyam2002000:
This has a download link lol and also its a newer one. i had been testing it out for 3 days just for to be sure
[Galaxy S II I9100G Android Development] neerajganga:
Keep up the good work :)
[Galaxy S II I9100G Android Development] ICS_XD:
Atleast DOWNLOAD link is dere :)

hey bro u port it or made it from sources ??

i also want to develope this typ of rom :)
[Galaxy S II I9100G Android Development] fuss132:
Well thats a bit weird now ^^
[Galaxy S II I9100G Android Development] samyam2002000:
Hey fuss saw you rom. but iad been testing this rom for last three days. so i could not resist releasing it. Its built on sources and has few cherry picks from Root box.
[Galaxy S II I9100G Android Development] neerajganga:
built from source
[Galaxy S II I9100G Android Development] fuss132:
Yes dito mine too ^^ i just tested it today and would have releae the dl this afternoon ^^
[Galaxy S II I9100G Android Development] ICS_XD:
fuss why u make old one ???

why not the latest one ??
[Galaxy S II I9100G Android Development] fuss132:
It is the latest one ^^ I just mistoke 3.0.1 and 3.3.1

Its totally the same ^^
[Galaxy S II I9100G Android Development] neerajganga:
fuss u had buit it from source or ported ?
[Galaxy S II I9100G Android Development] fuss132:
Of course source
[Galaxy S II I9100G Android Development] Infinite96:
This rom is smooth :D Battery friendly :P Nice one Samyam200200 :D

---------- Post added at 06:53 PM ---------- Previous post was at 06:50 PM ----------

Well...Everyone has their own opinion :P Maybe he likes old build :D
[Galaxy S II I9100G Android Development] fuss132:
Again its not the old its the same ^^

We have two identical ROMs now :D I think I will close my thread and let him do the work :P
[Galaxy S II I9100G Android Development] Infinite96:
LOL...:eek: You should release Horsepower 2.1.9 for it then XD . Oh yea ... Sound problem on horsepower :eek:
[Galaxy S II I9100G Android Development] iXanza:
Aww. I was gonna wait for yours . That's where my loyalty stands.
[Galaxy S II I9100G Android Development] Infinite96:
Its just the same :P
[Galaxy S II I9100G Android Development] ly123131426:
someone plz upload it to dropbox or google drive?the download links cannot be reached in China.
[Galaxy S II I9100G Android Development] ICS_XD:
Man porting is not easy as you think I know compiling is harder but it never means its easy as A **** .
[Galaxy S II I9100G Android Development] bluefa1con:
lets get real whats the worst that can happen if u are porting a rom

it doesnt boot, you use adb, find the issue and fix it

compiling and making a new rom is a different story

you need to rebase many patches learn the build system, using linux and if somehow build breaks go through the new changes and see if they break the build

some advice from Cyanogen http://xdaforums.com/showthread.php?t=667298

not saying that you are not contributing but quality roms > bulk of roms

learning stuff ground up will be good for you in future if you want to make a difference for a community
[Galaxy S II I9100G Android Development] iXanza:
Been trying to tell him that

Sent from my GT-I9100G
[Galaxy S II I9100G Android Development] ICS_XD:
Man if you saying that your ROM has quality but not mine than you are totally wrong .

I m not saying that you ROM don't have quality I my self used root box it was seriously good n it is . But when I port a rom I always choose vanilla cm base n Vaniila Aokp base n I don't think any other rom than cm ROM or Vaniila built can give you Performance .

OK u compile from sources hmmm

1. Libs

2. Bin

3. Xbin

4. Framework XML files

.

Rest thing like

Vendors

Tts

These are device specific you can't use i9100 ones m I right ?

Now apps

Apps must be off the ROM you compiling as you doing Rootbox so root box apps OK.

Now my porting

1.Apps

2. bin

3. xbin

4. Init.D scripts

5. framework .

These are from the Port ROM as in case i9100 cMiui

The rest Vendor files . Usr and tts basic permissions GPS.conf (device specific ) these are from base .

Man if I m right in above tell me diff in your and mine output .

Thanks
[Galaxy S II I9100G Android Development] fithryd:
Yup,totally agree..link plss
[Galaxy S II I9100G Android Development] ICS_XD:
I uploaded it on goo.im dont know where it gone not showing :(
[Galaxy S II I9100G Android Development] fithryd:
Name of file? I'll try look for it.
[Galaxy S II I9100G Android Development] Haxer87:
Goo.im has problems these days....use mediafire dude...
[Galaxy S II I9100G Android Development] Infinite96:
Oh yea :D Codename 3.6.0 :D Direct to ICS XD .. PM us the link :D
[Galaxy S II I9100G Android Development] fithryd:
I need it too..thanks:thumbup:
[Galaxy S II I9100G Android Development] :
I will update my sources and compile cna ;)
[Galaxy S II I9100G Android Development] gp545:
:cool: :D
[Galaxy S II I9100G Android Development] iXanza:
That's why you're my favorite developer. Haha :D
[Galaxy S II I9100G Android Development] fauzi_91:
Yeay! Hope that by tomorrow these will be done..:D:p
[Galaxy S II I9100G Android Development] Black_Prince:
Please compile CNA and bring us the updates....

Thanks in advance...
[Galaxy S II I9100G Android Development] Infinite96:
Thanks Fuss :P CNA 3.6.0 is from u :P XDDD
[Galaxy S II I9100G Android Development] CRY1S1S:
Thanks..:good:
[Galaxy S II I9100G Android Development] gopzzz:
Yes. Waiting longer for the update. Make it as early as possible
[Galaxy S II I9100G Android Development] ssettor:
Cant w8..:p
[Galaxy S II I9100G Android Development] iXanza:
Goodluck bro. I'm here to test for anything you need :D
[Galaxy S II I9100G Android Development] iXanza:
@fuss132 any ETA on this?
[Galaxy S II I9100G Android Development] :
I solved my unified kernel problem yesterday :D no time for cna.. maybe today if everything works. But you just have to download the sources and compile it that's very easy
[Galaxy S II I9100G Android Development] iXanza:
Haha I have no idea and no time sadly. School is a killer.

Sent from my GT-I9100G