yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Yank555:
14, excellent, will have to test closer to my access point ;)

I really can't complain, my Internet xDSL is 30mbps/10mbps on paper and for real (on my PC via cable), and for a reasonnable pricing, just under 50€/month including phone and national flat calling (landlines only), very competitive international prices.

Was about time that changed, we've been running way below whatever I saw in other countries, but this offer in octobre last year was a real WOW, so no hesitation ;)
[HD2 Android NAND Development] hypergamer1231:
u might find my question stupid but is it unlimited downloads or there is a limit
[HD2 Android NAND Development] Xylograph:
Keep in mind that besides the kernel (that will need the proper drivers etc.) there will also have to be ROM changes with additions and removals of libraries etc.

I think if Dorimanx would build a (cm9/aosp) rom from the ground up including the kernel and rom changes will give much better result to be honest..

There are a lot of sources for this to be found in the Desire/Nexus one forums that could make things easier for dorimanx I think... Correct me if I am wrong.

Couple of examples :

https://github.com/dk-zero-cool (cm9)

https://github.com/ics-passion-dev (aosp)

EDIT :

Believe me Dorimanx,

If you can get HWA going on ICS for HD2 it will be better/faster than CM7 Gingerbread will ever be..

I can safely say that because I have seen the difference on my wifes ZTE Blade..

Check this movie example if you have some spare time and keep in mind this device only have a ARMv6 600 Mhz processor..
[HD2 Android NAND Development] Yank555:
Flat, so no limits whatsoever.
[HD2 Android NAND Development] Mr.Oug:
You are one hell of a lucky guy...!!!
[HD2 Android NAND Development] Charmacas:
Hey Dori,

I would like to report again about 6.6C. In comparison with 5.7 the kernel runs slower. The apps are starting slower. And even if others may do not have this problem: The typing with my SwiftKey Keyboard has a delay which confuses me a bit. As always... I don't know if this report helps you in any way but I hope so. ;)

I tested with Typhoon 3.8.0 with and without ZRAM activated.

Gesendet von meinem HTC HD2 mit Tapatalk 2
[HD2 Android NAND Development] djsolidsnake86:
http://dorimanx.chipin.com/any-hd2-phone-to-help-me-in-developing

we are at 90%

and dorimanx have already a donated hd2 on the way
[HD2 Android NAND Development] dorimanx:
News update!

Kernel For SG2 has it's own tread now!

HERE

If contain kernel from today, starts with 1.0 version! :)

Have fun!
[HD2 Android NAND Development] iPAQ 6515a User:
Looks like you started it in wrong section :eek:

Unless you have 'G' at the end :D
[HD2 Android NAND Development] sam razzy:
Yup..u stated in wrong section...

TapaTalk Gnex Galaxy Sii
[HD2 Android NAND Development] dorimanx:
Thanks! :) moved to correct one!

and updated link.
[HD2 Android NAND Development] sam razzy:
You know what I actually was worried when someone commented to remove the thread... I even did a thread on general stating that the thread should be moved... hmm.. now m so happy...

TapaTalk Gnex Galaxy Sii
[HD2 Android NAND Development] pappt:
USB Storage

Hi!

If i copy files via usb cable, the files only visible after restart...i use 6.5D kernel...
[HD2 Android NAND Development] Looki75:
Hey Charmacas,

I observe the exact same thing than you!

And I can prove it; I have a Tasker profile which is activated at "screen off" event; it takes 1.5 longer to execute with kernel 6.6 than with kernel 5.7.

All other Tasker profiles suffer too from slower start and execution - not only the "screen off" one...

Dorimanx, could you make next releases as fast as 5.7?
[HD2 Android NAND Development] dorimanx:
i will try, i have added some more ported code from cm9. to hd2,

soon i get my cool hd2, then i can really forward in fixing things.

Sent from my GT-I9100
[HD2 Android NAND Development] elesbb:
anyone notice beta 6.6c with wifi, i would get disconnected(due to interference from cordless cell phones) but in order to reconnect i have to either turn off wifi or open the wifi settings. Anybody else notice this?
[HD2 Android NAND Development] chineel:
No I am used to be on WIFi 24/7 but never faced this problem, I Using cordless at home. please check your channel of RF in cordless
[HD2 Android NAND Development] elesbb:
I know, theres nothin i can do bout the cordless phones, but what happens is if i leave my wifi area and it disconnects, then i get back in the area, i have to either open up wifi settings, or turn wifi off then on in order for it to connect.
[HD2 Android NAND Development] themadproducer:
Last time I had something like that happen to me...it was a simple glitch. I was uing a Power Widget or Wifi widget to enable WIFI module (can't remember which one specifically). To correct the issue, I took the long route /settings/wireless & net.../and disabled wifi...waited...then re-enabled it.
[HD2 Android NAND Development] elesbb:
Hmmm, I only use the notification pull down toggle switches on cm7 ROMs... if that's what's causing it I'll live with it ^-^
[HD2 Android NAND Development] Hammerfest:
Dorimanx:

On my Tablet (i know different then phone, but im asking anyway), I use a kernel that has the following, and I wanted to see if maybe you could port it to our HD2's

"1.0-Veno Add TCP_VENO as default ipv4 Congestion Control Method"

with a link to "general" info here: http://www.ie.cuhk.edu.hk/fileadmin/staff_upload/soung/Journal/J3.pdf

I along with others using the kernel have noticed improved throughput, I dont know what your kernel used, but thought id ask about it

"add exFAT and NTFS support"

IIRC, your kernel already has NTFS support, so I guess Im wondering if exFAT support is possible, its got better read/write and iops in all tests ive done and I actually prefer to use it over NTFS and FAT32 whenever I can (says all my HDD's except boot drive in my PC, and all my flash drives)

and maybe if you have a chance ala some free time, take a look at the BFS updates to see if its fixed for us... I am one of the few who didnt have any SU issues with BFS, and actually use a kernel on my sisters Evo Shift that has it working fine... also, SuperSU is out now and quickly replacing SuperUser so maybe a new round of testing with the new app+su bin might be in order :D

Either way, thanks again for all your work and I hope you get your HD2 soon :D
[HD2 Android NAND Development] dorimanx:
i need to find the exfat code, its not included in kernel,

about bfs, its works fine with ics :)

so its can be tested.

and the new superuser maybe will act differently.

i will run the tests as soon as i can.

i need device. its already in postoffice.

they will ask to take it soon, and tell me where to go.

Sent from my GT-I9100
[HD2 Android NAND Development] themadproducer:
Yes that's it. It's called a Power Widget withing CM Settings.

For me, I think it was just a stuck glitch of sorts. Once I fixed it by toggling wifi on/off in as previously mentioned, the power widget worked again as normal.
[HD2 Android NAND Development] pirlano:
28$ to the goal, and dorimanx will be able to buy a new HD2!!! :D http://widget.chipin.com/widget/id/3b367483f9a8bb9c

GO GO GO :D
[HD2 Android NAND Development] securecrt:
dorimanx ,

I have made the adreno 200 kgsl driver (add a new drivers/gpu/msm ) compiled with your source. It boots up.!!

I am trying to make it work with Qualcomm's ICS userspace driver in ICS rom.

but a lot of errors in Logcat messages but at least the /dev/kgsl-3d0 has already there.

I think this the first step to enable the HWA for HD2 :)

E/Adreno200-EGLSUB( 279): GetBackBuffer() handle base address is NULL

E/Adreno200-EGL( 279): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC

E/Adreno200-EGLSUB( 279): GetBackBuffer() handle base address is NULL

E/Adreno200-EGL( 279): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC

E/Adreno200-EGLSUB( 279): GetBackBuffer() handle base address is NULL

E/Adreno200-EGL( 279): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC

E/Adreno200-EGLSUB( 279): GetBackBuffer() handle base address is NULL

E/Adreno200-EGL( 279): <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC
[HD2 Android NAND Development] Xylograph:
Nice ! do you have any test material (kernel) ? If you want I can help you test things..

About the logcat.. Have you included eglsubAndroid.so in your test rom ?
[HD2 Android NAND Development] Rick_1995:
LOL :D

You can't just add a folder and expect it to work...

You have to edit makefile, kconfig remove headers from /drivers/video/msm (if you haven't done this, the compiled kernel is still using older kgsl)

fixup board file for kgsl-3d0 platform resources

update to the newer android pmem for the new kgsl memory allocator

I am working on tiamat-kernel for leo, and once this is done i will move on to the linux 3.3 from rhodium guys, though they are using older kgsl since rhod has adreno 120 so will have to fix that.

If i go underground suddenly due to my exams, i will attach here my latest diff against the ics branch of tiamat.

The one attached is a work in progress, so don't just apply and expect it to compile, leave alone run on the device.
[HD2 Android NAND Development] Xylograph:
Hi rick,

Since you have quite some knowledge about this and you already told us where to look for things like merging the HWA stuff Drewis and Tiamat already worked out..

How difficult is it really to merge this to our older .32 or .35 kernel..?

I have never tried something like that, but am willing to try it.

And with all due respect.. couldn't you make us a (test) kernel with these changes for us so we can fool around before diving in the 3.3 kernel which could take another year of development if I look at the past attempts of 'upgrading our kernel' ?

Thanks
[HD2 Android NAND Development] securecrt:
Yes

I know what you are talking about.

I changed some Kconfig files and removed the /drivers/video/msm/kgsl dir

and I am sure the new kgsl driver has already been included in the zImage.

I am also trying to merge the leo files into the tiamat-kernel it is 2.6.38 baseline.

but seems lots of files need to be changed.

so I backport some 2.6.38 base files into our 2.6.32 :) hope it can work. still testing now.
[HD2 Android NAND Development] elesbb:
Meh, its a bummer that causes it to not auto connect again, but its not that big a deal. Thanks for the info!!!
[HD2 Android NAND Development] Rick_1995:
It is not difficult since we already have core device drivers from cotulla and markinus, just have to modify them a bit for mainline changes. All you will need is some knowledge about the chipset, it's working and a good diff tool.

Yes, i will go to 3.3 only after finishing this one and poop loader.

Have you updated pmem ?
[HD2 Android NAND Development] securecrt:
View attachment board-htcleo.c

I have attated the board file.
[HD2 Android NAND Development] Rick_1995:
pmem is not in board-htcleo.c

pmem is android's memory allocator, in the newer kgsl they use it for allocating memory instead of using staticly allocated/reserved memory which saves memory when much of graphics memory is not used.
[HD2 Android NAND Development] securecrt:
Thanks! I will try to back port that part.
[HD2 Android NAND Development] Rick_1995:
Off to sleep,

Things left to do

1) fix /arch/arm/mach-msm/include/mach/remote_spinlock

2) import and fix board files

3) fix makefile(s), kconfig(s) and htcleo_defconfig

4) import all leo specific drivers

5) review what i have done till now

below is the patch if someone wants to add on to it,

git clone git://github.com/drewis/tiamat-kernel

cd tiamat-kernel

git checkout ics

patch -p0 < tiamat.patch

work work work

git diff --no-prefix > ~/tiamat-new.patch
[HD2 Android NAND Development] dorimanx:
hi, thanks for great progress with drivers.

i will get my hd2 device in sunday, we have holidays and post office closed.

i will join to quest :)

and help how i can.

Sent from my GT-I9100
[HD2 Android NAND Development] Xylograph:
Wow this is finally getting shape ! You sir, should make a donate button for a little extra scholarship ;)
[HD2 Android NAND Development] Rick_1995:
Log says it all, either the allocation handler of kgsl is bad or the new pmem is not working well with the kernel, mostly the first one as if it was pmem, other android stuff would complain as well, check dmesg for pmem output and load some printk(s) in the kgsl memory allocation handler to see what is happening

securecrt, I hope the following commits will help you ;)

commit 1

commit 2

commit 3

commit 4
[HD2 Android NAND Development] Xylograph:
I/Adreno ( 125): open(/dev/kgsl-3d0) failed: errno 38. Function not implemented

That seems to be a problem ?

Maybe this seems like a strange proposal, but have you considered trying to boot a desire cm9 rom ( build with HWA implementation ) with your initrd.gz and zimage on our HD2 ?

Our hardware is quite similar..
[HD2 Android NAND Development] securecrt:
<4>Memory policy: ECC disabled, Data cache writeback

<7>On node 0 totalpages: 124864

<7>free_area_init_node: node 0, pgdat c0568bb0, node_mem_map c0bb3000

<7> Normal zone: 512 pages used for memmap

<7> Normal zone: 0 pages reserved

<7> Normal zone: 65024 pages, LIFO batch:15

<7> HighMem zone: 464 pages used for memmap

<7> HighMem zone: 58864 pages, LIFO batch:15

<6>allocating 33554432 bytes at c0f8a000 (1278a000 physical) for sf pmem arena

<6>allocating 42991616 bytes at c2f8a000 (1478a000 physical) for adsp pmem arena

<6>ram_console: found existing buffer, size 58831, start 58831

<6>console [ram0] enabled

<4>Built 1 zonelists in Zone order, mobility grouping on. Total pages: 123888

<5>Kernel command line: rel_path=ICS

<6>PID hash table entries: 1024 (order: 0, 4096 bytes)

<6>Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

<6>Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

<6>pmem: Initializing pmem (user-space) as cached

<6>pmem: Initializing pmem_adsp (user-space) as cached

<6>pmem: Initializing pmem_venc (user-space) as cached

<6>spi_bma150_probe: G-sensor connect with microP: start initial, kvalue = 0x0

<6>msmfb: full update completed

<6>msmfb: turning on panel

Ok I will turn on the printk in kgsl later. too sleepy.... now

thanks
[HD2 Android NAND Development] Rick_1995:
!!!! you might have included the new pmem driver but you haven't used it in board file, look at my previous response and the commit's linked for further help. Also use the egl libs from the desire hwa builds + adreno libs from qualcomm (armv7) or the ones in desire build.

running from haret can be either a very good or a very bad idea because of the fact windows mobile and haret may initialize hardware differently than just spl + mag/lk
[HD2 Android NAND Development] securecrt:
your suggestion is good . I have sent you the latest kernel to your email. hope you can do some test. I am too tired today.

---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------

the pmem should be used in the board file.

static struct android_pmem_platform_data mdp_pmem_pdata = {

.name = "pmem",

.start = MSM_PMEM_MDP_BASE,

.size = MSM_PMEM_MDP_SIZE,

/* .no_allocator = 0,*/

.allocator_type = PMEM_ALLOCATORTYPE_BITMAP,

.cached = 1,

};

static struct android_pmem_platform_data android_pmem_adsp_pdata = {

.name = "pmem_adsp",

.start = MSM_PMEM_ADSP_BASE,

.size = MSM_PMEM_ADSP_SIZE,

/* .no_allocator = 0,*/

.allocator_type = PMEM_ALLOCATORTYPE_BITMAP,

.cached = 1,

};

static struct android_pmem_platform_data android_pmem_venc_pdata = {

.name = "pmem_venc",

.start = MSM_PMEM_VENC_BASE,

.size = MSM_PMEM_VENC_SIZE,

/* .no_allocator = 0,*/

.allocator_type = PMEM_ALLOCATORTYPE_BITMAP,

.cached = 1,

};
[HD2 Android NAND Development] Xylograph:
Received :) Haven't flashed it yet though.. still comparing ramdisks with the one from tytung and there are a lot of differences.. is that only because of you using haret/sd ?

Can I use tytung ramdisk..?

What are the most important changes in it ?
[HD2 Android NAND Development] securecrt:
init.rc

add the two lines

chmod 0777 /dev/kgsl-3d0

chmod 0777 /dev/genlock
[HD2 Android NAND Development] Xylograph:
Ok after adding those 2 lines to init.rc/flashing kertnel and all the provided libs ..

My rom boots (without bootanimation) and is very slow and my logcat is flooded with :

20:38:27.005 Error Adreno200-ES11 143 <qglDrvAPI_glTexImage2D:1913>: GL_OUT_OF_MEMORY
20:38:27.005 Error Adreno200-ES11 143 <qglDrvAPI_glTexSubImage2D:2055>: GL_OUT_OF_MEMORY
20:38:27.005 Error Adreno200-EGLSUB 143 GetBackBuffer() handle base address is NULL
20:38:27.006 Error Adreno200-ES20 143 <gl2_surface_swap:41>: GL_OUT_OF_MEMORY
20:38:27.006 Error Adreno200-EGL 143 <qeglDrvAPI_eglSwapBuffers:3345>: EGL_BAD_ALLOC

Anyway here is +4000 lines of logcat from the boot

http://pastebin.com/iVs8MxAW

I don't think I can do much 'rom-wise' to make it better yet..at least it boots :) rotating screen takes about 5 seconds hehe
[HD2 Android NAND Development] dorimanx:
i like the posts, now its real development battle zone :)

keep it up, great work!

Sent from my GT-I9100
[HD2 Android NAND Development] Xylograph:
About time.. :D
[HD2 Android NAND Development] Rick_1995:
upload your "git diff" ?
[HD2 Android NAND Development] Xylograph:
I think he went to bed..

Anyway..Rick since you are still awake.. If I may ask..

I was just comparing a Desire HWA rom with one of my AOKP roms and saw a couple of libs which are missing on mine..

except the libgenlock I also saw libhwui.so..

I suppose that one is needed as well to get things going..

Anyway with the test kernel securecrt provided me it doesn't make any difference regarding speed :)

Ah well one step at a time..
[HD2 Android NAND Development] Rick_1995:
It won't, not alteast till opengl is allocated memory to work with :p
[HD2 Android NAND Development] frumpy:
I see people have good results using this kernel with Tytung's ICS ROM.

I'm using the Mar 9 version, downloaded 6.6C kernel and installed via CLK recovery. It seemed to go fine but would not reboot. I booted into recovery and restored from backup fine.

Am I missing a step? Would like to give the kernel a try.

thanks!

Paul
[HD2 Android NAND Development] Xylograph:
True, ah well I'm happy you and others are working on it now :)

Dorimanx, your kernel 6.6c is working fine and stable with my ICS rom btw.

The only problem was after using gps I got a 60ma wakelock..
[HD2 Android NAND Development] KyJelly69:
hush... the grownups are talking.
[HD2 Android NAND Development] securecrt:
I think the problem is /drivers/video/mdp.c need some changes
[HD2 Android NAND Development] Hammerfest:
Did we ever get a final verdict on the GPS wakelock? I had it prior to using Dorimanx's Kernel, and mentioned it in the GPS thread, but was told that there "was no issue" with what was provided causing it...

So... is the ROM? is it the Kernel? or is it REALLY the GPS stuff??????
[HD2 Android NAND Development] Yank555:
It obviously is the kernel, since I only have since somwhere around 4.5 or so.

But if you don't use WiFi localisation, there's a workaround to it. You need to use TitaniumBackup to freeze "Location Services" (that's not the correct name, I don't have my HD2 handy to look it up).

Solved it for me, and I had the wakelock EVERY morning before.

JP.
[HD2 Android NAND Development] themadproducer:
You run Hyperdroid rom right Yank?

because I don't see a file named anything close to Location Services via TB in Dx's rom. Maybe that' why I never got that particular issue?
[HD2 Android NAND Development] Looki75:
Yank,

I am using Dorimanx ROM, and I had the GPS wakelock exactly 2 times, which is very few, when you consider that I have the same charging pattern than you:

* every night, I plug the phone at 23:30 for charging overnight,

* BatteryMonitor widget shows that around 2am, I reach the 100% charge

* but the phone keeps plugged until 6:30am

* at 6:30am, Current Widgets shows 0mA, as expected

Even doing that every day, I almost never had the GPS wakelock.

This is not good news: the bug is hard to reproduce, except for you.
[HD2 Android NAND Development] Xylograph:
@securecrt

I have looked that file up on github and there haven't been any changes/commits to that file for a year.

Maybe you can upload your diff file for Rick so he can take a look ? :)
[HD2 Android NAND Development] Hammerfest:
where would I find this entry?

also, this used to happen on tytung's rom, as well hyperdroid... so your saying that killing this "location services" would have prevented the GPS 60ma wakelock on every rom and kernel? (thus invalidating the fact that its the kernel) considering Dorimanx didnt have a kernel when I was using Hyperdroid...
[HD2 Android NAND Development] Xylograph:
I use GPS sporadically..

When I did use it some days ago I forgot to turn the GPS off (if that even matters)

Next morning I saw a drained battery (38% left) with at least 60ma on my current widget..

So turning off Google Locationservice is a workaround ?

I will try it out, Thanks.
[HD2 Android NAND Development] dorimanx:
yes fix it freezing the apk of location in system app, then you loose location by network, but no wakelocks.

i suggest to update this apk from ics google apps package, and see if its resolved.

Sent from my GT-I9100
[HD2 Android NAND Development] Yank555:
Yep, Hyperdroid 6 extreme.

The app to freeze is called "Network Location 1.0.0" in Titanium Backup.

BUT !!

I had the damn wakelock this morning, AGAIN :( So it's not that afterall ...

JP.

---------- Post added at 10:34 AM ---------- Previous post was at 10:21 AM ----------

It is very strange, and when I stick to exactly what you describe, the second I pull the HD2 from the wall charger, the wakelock begins (eg. BetterBatteryStats says the lock is on from that moment on).

To show the drain you'd need to wait for the next read obviously, since BatteryMonitorWidget only does it once every x minutes (config).

Don't ask why I have it so systematically :(

I will try to keep having a look at this to confirm if it has been solved, since I seem to be the only one to be able to reproduce it once every 24h ;)

But I have a good/bad news, as of today I am the owner of an htc Sensation XE ... so my HD2 will no longer be my daily within a few days (the time I need to S-off/root and find a good ROM for the XE ;)).

I will probably sell one of my 2 HD2s but keep the other one, it's been too good a companion to just give it away, I know I'd regret it shortly after if I let it go :D

JP.
[HD2 Android NAND Development] Rick_1995:
As xylograph suggested, have you tried using the shared objects from desire hwa enabled roms instead of the qualcomm supplied binaries ?

Compare the kgsl driver and it's related pmem, kgsl structures in board files from www.github.com/drewis/tiamat-kernel

Also, please wrap such logs, code in [ CODE ] [ /CODE ] blocks..

Here is my latest diff, have to fix board files, include leo-specific drivers and review the code.
[HD2 Android NAND Development] Xylograph:
I found the wakeup error entry in kgsl.c so it probably has something to do with that ?

static int kgsl_open(struct inode *inodep, struct file *filep)
{
int result;
struct kgsl_device_private *dev_priv;
struct kgsl_device *device;
unsigned int minor = iminor(inodep);

device = kgsl_get_minor(minor);
BUG_ON(device == NULL);

if (filep->f_flags & O_EXCL) {
KGSL_DRV_ERR(device, "O_EXCL not allowed\n");
return -EBUSY;
}

result = pm_runtime_get_sync(device->parentdev);
if (result < 0) {
KGSL_DRV_ERR(device,
"Runtime PM: Unable to wake up the device, rc = %d\n",
result);
return result;
}
result = 0;

unfortunately I am already using the latest one... I will freez or uninstall it, but I hope you can look at it..

It seems the graphics aren't getting any memory assigned ?

---------- Post added at 10:45 AM ---------- Previous post was at 10:44 AM ----------

Already tried that Rick... same results unfortunately (as far I could see exchanging the libs)

EDIT : Though it couldn't hurt to try booting a HWA Desire rom.. I will look at it ;)

---------- Post added at 11:21 AM ---------- Previous post was at 10:45 AM ----------

Btw securecrt if you have any new developments you would like to have tested just email me ;)