[Q] NVIDIA PerfHUD ES on Galaxy Tab 10.1 Honeycomb (3.1) - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hi,
has anyone managed to run Nvidia's PerfHUD ES on Galaxy Tab 10.1? I have come to the conclusion that the instrumented drivers need to be copied to /system/lib/egl on the device, then egl.cfg (in the same directory) must be modified accordingly. There is a site that offers these library files for Froyo and Gingerbread, but not for Honeycomb.
I tried downloading the Tegra Android Honeycomb (3.2) OS Image from Nvidia's Website and take the driver files from there but I failed extracting the system.img file. Anyway, I'm not sure these 3.2 files would be compatible with my 3.1 system.
Any ideas?
Edit: I had included all the relevant links here, but since I'm a noob I had to remove them. But don't say I didn't try.

Sorry for the bump. Doesn't anybody have experience with this? Maybe there is a better subforum to post this?

Related

[Q] Honeycomb on Archos Gen 8 already available?

I just stumbled over this page:
http://phonetipstricks.com/archos-101-tablet-update-to-android-3-0-honeycomb#
Is it true? Does it work? Or is it a fake or even worse, malware?
It is the same thing we are already talking in 2 other postings.
Just to put the binaries of the Emulator Image onto the archos doesn't work.
The Poster also didn't say that you can't unlock, as the screen is not responding.
We need the Sourcecode of HoneyComb not the SDK.
The SDK only has the api to develop Software for HC.
fzelle said:
It is the same thing we are already talking in 2 other postings.
Just to put the binaries of the Emulator Image onto the archos doesn't work.
The Poster also didn't say that you can't unlock, as the screen is not responding.
We need the Sourcecode of HoneyComb not the SDK.
The SDK only has the api to develop Software for HC.
Click to expand...
Click to collapse
Was suspicious too since it was only the unlock screen mentioned. Was wandering it it was a leaked HoneyComb release for Archos Gen 8, but now that's clarified. Thx!
Honeycomb on Archos gen8 [development thread] [early stage]

Xoom apks

Ok so I have the Full xoom dump. When I try to install any of the apk's in it i get "Their is a problem parsing the package". Is their any way I can get them to install? Would the system dump help port honeycomb to the Archos 101?
I'm pretty sure the problem is you are coming from an entirely different android build. Sort of like trying to open a froyo app on android 1.6.
For half a second I had the same thought as you - "hey, we could have tablet optimized apps on the Archos by using the xoom apks!" but then I realized the problem. I couldn't even begin to know how to get them to work.
Yeah, there is no way to make those work. They have a minimum version of 3.0 in the bindary, so you would need the source code and some major programming to make it work under 2.2 as I am sure they utilize API's specific to Honeycomb.
Moved to general as not android development

[IDEA]Porting Android 3.2 to Folio 100

I'm NOT EXPERT, I'm ONLY TRING TO HELP and SORRY IF I MADE SOME MISTAKES!
I have some ideas for porting android 3.2 to Folio 100 but I can't do all myself - I need some help.
My first idea is:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and decompile zlmage inside HC kernel(if that tool existe or find it's kernel source, add changes from android 3.2 kernel and recompile it).
---------------------------------------------------------------------------------------------------------
1. This idea is really hard to realise because kernel(I don't think that tool existe) but it's convinient(we'll finish it in short period with little work).
2. For this idea first we need to add changes from android 3.1 and after that from android 3.2.
3. I NEED YOUR HELP to find WHAT ARE CHANGES and TO DOWNLOAD
THEM for adding them to OUR build(First android 3.1 changes and after android 3.2).
For system that isn't problem but for kernel it is. The most detiled list of changes can
be find at Android SDK site but I think that we can't download them.
4. I think that mblaster know a lot of kernels and compiling it won't be problem for him.
----------------------------------------------------------------------------------------------------------
My second idea is similar to first one:
To add changes made in android 3.2 system(framework, apps etc.) to our Honeycomb from SDK or Xoom and compile android 3.2 tegra kernel from
Android Git or from other sources.
----------------------------------------------------------------------------------------------------------
1. I think that this idea is the best if mblaster help us or some one else that know a lot
of kernels.
2. Google won't relise full source of android 3.2 before pushing up android 4.0 aka
Ice Cream Sandwich to shops.
----------------------------------------------------------------------------------------------------------
I can port system itself(it will be faster if someone make a list of changes) but kernel is
a problem. I don't know much about kernels and because it I post first idea.
If you have new ideas or you don't agree with me or want to help me, please, post here!
EDIT: Android 3.2 might work with our HC kernel.
Sent from my Folio3x using Tapatalk
good idea +1
Thanks.
Sent from my Folio3x using Tapatalk
Not interested?
Sent from my Folio3x using Tapatalk
nice idea..
if u write drivers and kernel change, some other developer can use your work alot.
anyone writing all the drivers for folio will make toshiba happy, as they did not do it..
so if you make all this happen and write the drivers , i am sure folio will once again be a good tablet.
the development is something that takes companies 3-6 months to do, so you will be back in december 2011 or maybe early 2012 with your release?
Can someone compile Tegra 3.2 kernel from here? I tried but without success. I'm porting system now.
I tried to unyaffs FolioComb 3xx v2.0 image bu I got 'Segmentation fault'???
I succefully unyaffsed Android 3.1 and 3.1 SDK images.
I'll try to backup it from my tablet(I have FolioComb on it)
Nice to see someone trying to update folio 100, thanks to you and people in CM7 thead.
I don´t know about compiling so I cant help. But i keep an eye in this post.
Do you know anything about system?
EDIT:Nothing

FOR DEVELOPERS: Lib Files with HW Acceleration

Lately I have been getting many requests from HP Touchpad users to provide the lib files for the Le Pan II, which has the same specs (running Honeycomb 3.2.1) with hardware acceleration enabled.
This is supposed to help you somehow, so I really hope it does! If any developer finds use for this and would like to help our community by finding a root exploit for the Le Pan II, it would be greatly appreciated.
We can be found @ www.forum.lepanlife.com
And the entire system folder, including the lib files for the Le Pan II can be found @ http://lepanlife.com/system/
Hope it helps, enjoy
Thanks for this. Maybe this will help our devs with the OMX HW Acceleration issues on the Touchpad under CM9.
I went ahead and uploaded an archive of the system folder (I removed the index.html files, and renamed the buildpropv114.html to build.prop).
http://www.mediafire.com/?v5ytbam1ziwxo5a
Good luck with rooting the Le Pan II, it looks like a nice device.

i Have successfully compiled Samsung's SM-T580 kernel, how do i make the boot.img?

Hello,
First of all, this is my first post in the forum and my first time trying to compile an Android kernel.
My intention was to port Nethunter for my tablet, Samsung SM-T580 (Galaxy Tab A6 10.1 only wifi).
I have successfully compiled the original kernel offered by samsung and i have ended up with a file called Image, a file called Image.gz and a dts folder
I have extracted the original rom boot.img with mkbootimg_tools and i see a kernel file, a ramdisk folder, a ramdisk.packed file and a dt.img
For what i have found is that this must be a non standard thing, the way samsung manages this, and despite i have seen various guides on compiling samsung kernels, i haven't found anyone doing it straight from samsung sources.
I think that the dt.img part is solved with the dtbTool, but i haven't been able to figure out what to do with Image and Image.gz to get the kernel and ramdisk.
¿Can someone give me a lead on this? ¿Is it doable? ¿Should i look for other kernel instead?
Its been long time ago... But did you manage to compile the kernel?

Categories

Resources