yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] sambafr:
I try to search what HSPL4 (meaning SPL 3.03) brought that HSPL 2.08 didn't, I didn"t find anything, i guess the differences are too high up for me... and assuming that when they he talks about 3.xx roms in the thread under it's about winmo

http://xdaforums.com/showpost.php?p=5279236&postcount=4

Another thing Pongster ask for clk users not to post in Hyperdroid thread therefore i will ask my question here : I did not delete 02cache before updating to tytung r8. Everything is working fine (edit : FINE is a small word for Fabulous ,Insane speed ,No bugs, Economic on battery ; lol)... am i missing something, lucky or does clk1.3.3_system_100m_arif-ali makes a workaround? thanx for reply
[HD2 Android NAND Development] bhilgeman:
Please see my signature to know what I am running on my phone. I cannot get reboot to recovery or ROM Manager to work for the life of me. Can you give me a hand?
[HD2 Android NAND Development] A11-STAR:
Okay, I am guinea pig #1 :)

I need to install SDK, one sec.
[HD2 Android NAND Development] seadersn:
hi,

did you perform a "wipe data / factory reset" before installing tyweens typhoon zip? you can do a cache only format afterwards in cwm via "mounts and storage - format cache" to see if it helps. do the same with the misc partition please :)

was it a completely fresh install of tyweens ROM with flashing this kernel afterwards or was this ROM already installed and configured? can you please list the files in /system/etc/init.d folder and maybe have a look inside the 99complete script on your phone? eventually it wasn't overwritten or doesn't even exist :eek:

does "df -h" in terminal emulator or adb shell show up a line like

/dev/block/mtdblock4 5.0M 784.0K 4.2M /mnt/recovery and

/dev/block/mtdblock4 5.0M 784.0K 4.2M /data/cache/recovery

?

ahh... and which recovery did you install in rom manager? did it overwrite your current recovery and

if

: did you reflash one of the recoveries available in this thread? :D so much questions...
[HD2 Android NAND Development] arif-ali:
can you get back to me with the following in pastebin

ls -l /
ls -l /cache
ls -l /cache/recovery
mount
df
[HD2 Android NAND Development] bhilgeman:
init.d contains

00banner

01_modules

01sysctl

02cache

03firstboot

04modules

05mountsd

06mountdl

10apps2sd

11dalviklocation

20userinit

97ppp

97zipalign

98cpu_voltage

99complete

df -h produces

df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 205.5M 0 205.5M 0% /dev

tmpfs 205.5M 0 205.5M 0% /mnt/asec

tmpfs 205.5M 0 205.5M 0% /mnt/obb

/dev/block/mtdblock3 150.0M 125.0M 25.0M 83% /system

/dev/block/mtdblock5 728.0M 184.3M 543.7M 25% /data

/dev/block/mtdblock4 44.0M 1.3M 42.7M 3% /mnt/cache

/dev/block/vold/179:1

7.6G 4.6G 3.0G 60% /mnt/sdcard

/dev/block/vold/179:1

7.6G 4.6G 3.0G 60% /mnt/secure/asec

My fresh install of Typhoon started with 2.6.x I have flashed each update on top of those. For a while I was flashing hyperkernel v6 and last night I updated Typhoon to the latest and flashed Tytung r8 afterward.

The last time I tried ROM manager I chose Desire HD and it downloaded it and then said it installed it. I chose reboot to recovery from Rom Manager and it rebooted back to OS, I chose reboot recovery from shut down menu, it rebooted to the OS, I manually entered recovery and still had CWM 3.0.1.9

So what am I missing? I haven't opened up the 99complete script. What would I be looking for in there? I use linux 99% of the time I'm home, but don't know unix commands very well. I'm pretty much Gnome only :)
[HD2 Android NAND Development] seadersn:
k, delete 02cache OR 99complete and try again, for testing :) but i wrote this in my "kernel-post" ;)

but we should wait until arif has completed his cache script for this special case with this special initrd.gz. this is a much cleaner and better method; mine is a "dirty hack"...
[HD2 Android NAND Development] seadersn:
oops, sry, arif! overseen your post; bhilge, please follow his steps first ;) he is fitter than me :D
[HD2 Android NAND Development] bhilgeman:
link to your pastebin please?
[HD2 Android NAND Development] arif-ali:
I meant, can you run the commands, and put it on pastebin, but if you want mine, then here it is

ls -l /
ls -l /cache
ls -l /cache/
ls -l /cache/recovery
ls -l /cache/recovery/
mount
df

http://pastebin.com/4ucAR8vF
[HD2 Android NAND Development] bhilgeman:
See I'm retarded... Here's mine :) http://pastebin.com/sEsXTRTq

I thought it was like google code where I paste on your site. :)
[HD2 Android NAND Development] arif-ali:
ok, your proper cache partition is not mounted, and that's why it is not working

can you check the following 2 commands

cat /proc/mtd

ls /dev/block
[HD2 Android NAND Development] bhilgeman:
# cat /proc/mtd

ls /dev/blockcat /proc/mtd

dev: size erasesize name

mtd0: 00100000 00020000 "misc"

mtd1: 00500000 00020000 "recovery"

mtd2: 00500000 00020000 "boot"

mtd3: 09600000 00020000 "system"

mtd4: 02c00000 00020000 "cache"

mtd5: 2d800000 00020000 "userdata"

#

/dev/block:

loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5

loop1 loop4 loop7 mtdblock0 mtdblock3 vold

loop2 loop5 mmcblk0 mtdblock1 mtdblock4

#
[HD2 Android NAND Development] arif-ali:
ok

if you mount the mtdblock4, what do you get

mount -t yaffs2 -o rw /dev/block/mtdblock4 /mnt/cache

check if it is mounted by typing "mount"

if this doesn't work

mount -t auto -o rw /dev/block/mtdblock4 /mnt/cache

and check again, if it is mounted, let me know which one works. and give me the out put for

mount
[HD2 Android NAND Development] bhilgeman:
Doesn't look like either worked

# mount -t yaffs2 -o rw /dev/block/mtdblock4 /mnt/cache

mount -t yaffs2 -o rw /dev/block/mtdblock4 /mnt/cache

mount: mounting /dev/block/mtdblock4 on /mnt/cache failed: No such file or direc

tory

# mount -t auto -o rw /dev/block/mtdblock4 /mnt/cache

mount -t auto -o rw /dev/block/mtdblock4 /mnt/cache

mount: mounting /dev/block/mtdblock4 on /mnt/cache failed: No such file or direc

tory

#

# mount

mount

rootfs on / type rootfs (rw,relatime)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)

/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)

/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,r

elatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,

iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe

xec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=c

p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

#

Did I do this right?
[HD2 Android NAND Development] seadersn:
you have to create a directory first in /mnt

mkdir /mnt/cache

don't know of it's of interest or need, but the kernel i've posted is using the initrd.gz i've sent you, arif ;) if he is deleting your 02cache script it will work, because i've mounted cache partition (in 99complete) in another directory (/mnt/recovery) and linked recovery folder in it to /cache.
[HD2 Android NAND Development] arif-ali:
ok, yes, you did that right

try doing

mkdir /mnt/cache

if this doesn't work

then

mount -o rw,remount /

mkdir /mnt/cache

mount -o ro,remount /

after this repeat the steps in the previous steps

then run

mount

ls -l /cache/recovery

ls -l /cache/recovery/

I think this should work now

I am trying to understand what is going wrong, so that I can fix the 02cache script
[HD2 Android NAND Development] bhilgeman:
# mkdir /mnt/cache

mkdir /mnt/cache

# mount -t yaffs2 -o rw /dev/block/mtdblock4 /mnt/cache

mount -t yaffs2 -o rw /dev/block/mtdblock4 /mnt/cache

# mount

mount

rootfs on / type rootfs (rw,relatime)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)

/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)

/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,r

elatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,

iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe

xec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=c

p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

/dev/block/mtdblock4 on /mnt/cache type yaffs2 (rw,relatime)

# mount -t auto -o rw /dev/block/mtdblock4 /mnt/cache

mount -t auto -o rw /dev/block/mtdblock4 /mnt/cache

mount: mounting /dev/block/mtdblock4 on /mnt/cache failed: Device or resource bu

sy

# mount

ls -l /cache/recovery

ls -l /cache/recovery/mount

rootfs on / type rootfs (rw,relatime)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)

/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,noatime,nodiratime)

/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,r

elatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,

iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe

xec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=c

p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)

/dev/block/mtdblock4 on /mnt/cache type yaffs2 (rw,relatime)

# ls -l /cache/recovery

lrwxrwxrwx 1 root root 19 Mar 23 17:46 /cache/recovery -> /mnt

/cache/recovery

#

Sorry I should have told you I deleted my 02cache and 99complete files after seadersn told me to and before I started doing any of this with you...
[HD2 Android NAND Development] arif-ali:
ok, that should do it now, try rom manager now
[HD2 Android NAND Development] bhilgeman:
No dice... Man I really appreciate your time, I hate to waste it though... It rebooted back to the OS.

I went into ROM Manager, chose reboot recovery, it rebooted to the OS.

I went back to ROM Manager, chose flash CWM Desire HD, "Success" reboot recovery, rebooted back to OS

I manually booted into Recovery and I still had 3.0.1.9...

I'm all for keeping working on this with ya if you need the info for your script and have the time, but I hate to waste your time.... Want me to backup and wipe and try from a fresh install?
[HD2 Android NAND Development] Kameirus:
ok i just decided to try to boot into recovery from rom manager

and it worked perfect on the rom in my sig

except im using the tytung r8 clk
[HD2 Android NAND Development] seadersn:
in the newer ones arif's 02cache script is included and has to be deleted first. i believe it was a mistake putting my modified 99complete script into this r8-update.zip...
[HD2 Android NAND Development] seadersn:
ok, have a look:

kernel update

post update

now you should be able to reboot to recovery, as this is "standardized" now through tyweens standard initrd.gz (edited for ppp mode) which handles cache partition normal.

reflash of tyweens build and directly afterwards flashing the kernel update should work :)
[HD2 Android NAND Development] zach.antre:
I didn't had any problems with tytungs r8 that you posted yesterday (the one in my sign)...

I even tried it now again (reboot to recovery) and all worked fine.
[HD2 Android NAND Development] seadersn:
yep, but only if there isn't the 02cache script present in your init.d folder :(

arif's version of reboot-to-recovery-fix is much more comfortable and usable for much more builds. mice was a special version, only fitting my needs, which i wrongly made public, because it confuses more than it helps :)

http://xdaforums.com/showpost.php?p=12336136&postcount=4654

here is the updated kernel and partition layout for tyweens cm7, using his partition layout and initrd.gz, edited for ppp mode.

yeah, and now: gn8 :D
[HD2 Android NAND Development] arif-ali:
Just to le you know ...

I checked out the same rom, as you guys, with seadersn's kernel update, removed 99complete and 02cache and replaced with my new 02recov script below

02recov

and it seems to be working.

I managed to reboot to recovery, using normal reboot method, and reboot to recovery from ROM manager.

If someone does test it, let me know how it goes.
[HD2 Android NAND Development] seadersn:
yep, it works :)

the only problem left for ppl with small cache sizes now is: how to gain more cache size without the need of flashing a new partition layout...
[HD2 Android NAND Development] arif-ali:
btw, anyone who want to get rom manager working, without having to get asked which phone you are using and install another recovery, you can use the following method

After booting into the phone for the first time, you need to create the following file on your sdcard, and reboot the phone. Hopefully after this, the rom manager should work.

/sdcard/clockworkmod/.settings

with the following contents

{"is_clockworkmod":true,"current_recovery_version":"3.0.1.9","readonly_recovery":false,"recovery_timestamp":1300214577721,"flash_recovery":"flash_image recovery %s ; ","reboot_recovery":"","detected_device":"leo"}

I hope that helps
[HD2 Android NAND Development] lippa:
Okay i think i got a fair bit lost with all the v8 kernels. Im running seadersn v8 kernel he posted yesterday (first release). And i have working recovery. Should i be reflashing a different one?

Running HyperdroidGBX if that helps.
[HD2 Android NAND Development] seadersn:
@ lippa: nope, stay with that you've got already installed, it's ok :-) for me it's the best solution: cache is huge (rest of data partition) and reboot to recovery works (through linking recovery folder of cache partition into /cache folder, which is linked into data partition :ugly:

the new r8 kernel is suitable for "normal" roms with "normal" cache partitions. mine wasn't normal (only 5mb cache partition, not mounted, /cache folder in root linked into data partition; i had to mount cache partition manually via startup script (not through initrd.gz) and link the recovery folder inside this partition into /cache folder). complex sh*t, sry :(
[HD2 Android NAND Development] zach.antre:
Arif, 02recov is not included in seadersn fix.

what are the benefits by adding it?

I am sorry but i am a bit confused.

With new partition layout and fixed kernel patch provided by seadersn everything seems to work fine.

About the .settings in CWM it shows the version but it allows me to flash any other CWM version i want (i mean from other mobiles, it shows the list), since Leo is not in the list.

"Reboot into recovery" from ROM Manager and Red button works fine
[HD2 Android NAND Development] seadersn:
but 02cache is included in tyweens build ;) i've edited the 99complete file for getting this to work. as i said: dirty...
[HD2 Android NAND Development] zach.antre:
I see... so it's fine as is right now.

@Arif, did you find a solution for your kernel with this build? i really would like to try it with your kernel.
[HD2 Android NAND Development] DannyBiker:
Hello,

is there a way to flash clk (coming from MAGDLR Clockwork Recovery) using Ubuntu ?
[HD2 Android NAND Development] arif-ali:
There is, using the leoimg.nbh from SD card. But if you search the thread, cedesmith does not suggest, as potentially it can brick your phone.

I know some of the guys on this thread have use this method. And I use this method as well.

So if you do it this way, do understand the risks.
[HD2 Android NAND Development] arif-ali:
not yet, will have a look, probably sometime today
[HD2 Android NAND Development] DannyBiker:
Okaaaay, I'll wait for Windows...:D

Thanks !
[HD2 Android NAND Development] stirkac:
I hope my tutorial goes to first post or whatever. now that typhoon biuld is clk friendly i will update it... wait couple of hours:D
[HD2 Android NAND Development] l0rdsheva:
it's normal that even if i've downloaded (2 times to be sure :) ) the 1.3.3 version once flashed it say i've 1.3.2?
[HD2 Android NAND Development] lippa:
Just a heads up.. Might want to update the topic, since 1.3.3 has been out for awhile..
[HD2 Android NAND Development] stirkac:
i'm wondering where cede is myself... i guess busy with his own life. first thread should be updated as many things are different, one of them being version.

c'mon, we can't let magldr beat us :D
[HD2 Android NAND Development] stirkac:
okay i updated my tutorial with instructions for CLK typhoon :)
[HD2 Android NAND Development] D.O.C:
Holy crap man..... rom manager works with this... all functions except rom updates ofcourse, but we are able to flash, bacup, restore......thanks bro....!
[HD2 Android NAND Development] randasecret:
after using tytung r8 ppp update by seadersn with CM7

- ppp no more drops and it's fast

- rom manager is working great

thanks.
[HD2 Android NAND Development] tyween:
I used the boot.img that seadersn posted in this thread in my v2.8.0 build, I have been trying to generate one with tytung r8.1.. and having trouble. What am I doing wrong? I thought it would be pretty straight forward with mkbootimg... I was using this command:

mkbootimg --kernel boot/zImage --ramdisk initrd.gz -o boot.img

I must have missed something here :confused:

I was following this guide

I also tried the longer command line listed on this webpage to no avail.
[HD2 Android NAND Development] seadersn:
mkbootimg --cmdline "" --base 0x11800000 --kernel zImage --ramdisk initrd.gz -o boot.img

;)
[HD2 Android NAND Development] tyween:
Thanks, :) about to give it a shot.
[HD2 Android NAND Development] seadersn:
hit the button, don't type it xD it's written in the readme of source code of cLK; have a look at it :)
[HD2 Android NAND Development] seadersn:
new recovery 3.0.2.4 :)
[HD2 Android NAND Development] M..N:
I've been thinking maybe something could be implemented in the ppp wrapper, so that if the connection gets stuck/ it disconnects it automatically detects this kills it and resets it.

Just a thought.
[HD2 Android NAND Development] Nevod:
How much RAM is availible after booting with cLK?

It's known that MAGLDR leaves only 412mb out of 576, does the cLK leave all memory in there?
[HD2 Android NAND Development] xing7ba:
thanks you
[HD2 Android NAND Development] stirkac:
ram is there to be used. and imho bootloader doesn't do difference there as it only loads kernel pretty much
[HD2 Android NAND Development] Kameirus:
can i just flash tytungs new r8.1 or does it need to be setup or clk

reason im asking is i need to test something out and am going back to an earler rom version but would like to use his new r8.1

Thanks
[HD2 Android NAND Development] mattfmartin:
Yes you can flash it
[HD2 Android NAND Development] mattfmartin:
@Seadersn

Maybe you can answer this? I installed typhoon 2.8.0cLK and I lost the ability to reboot 2 recovery. I switched to one of the original kernels, rafpinga1.8_OC_NO SENSE. BECAUSE ITS THE ONLY ONE I GET A CONSTANT 3ma in standby. That's when I noticed I lost the reboot to recovery option. My question is why would switching a kernel make reboot to recovery stop working. I know that was the reason because I reinstalled the zip with the included tytung kernel and it worked. Once I switched again to rafpinga, that option was gone.
[HD2 Android NAND Development] seadersn:
first i want to say "because cedesmiths patches aren't in his git", but that's wrong. second thought: the ramdisk. did you use the same initrd.gz for both original kernel delivered with tyweens build tytung r8 and the new flashed kernel rafpigna 1.9? if not, i believe this is causing it.
[HD2 Android NAND Development] mattfmartin:
Ahhh that makes sense. I couldn't wrap my head around why switching a kernel would do that. Thanks for pointing that out. That WOULD he the only reason:p
[HD2 Android NAND Development] noellenchris:
There are a few threads from months ago that address this same issue. Honestly, it never really got much more stable. The dev LeTama worked on trying to fix PPP on the HD2 for months with many wrappers etc. Best bet is to figure out how to get RMNET to work. For that, we'll probably need Cotulla to figure it out...
[HD2 Android NAND Development] mattfmartin:
Just tryed rafpinga_1.9_oc_gb.... On typhoon. It didn't even boot. Anybody else have success with it? It didn't even have the ppp fix thing when it loaded. Think thats why it didn't work. Hopefully it gets fixed cause I love his kernels.
[HD2 Android NAND Development] wolfpack612:
yea that didn't work for me either. I created a boot.img for clk using the kernel in his zip and I think the initrd I'm using which I can't remember which one hehe. I was going to post my cwm zip right now but looks like I can't attach files only pictures with xda app :(
[HD2 Android NAND Development] yuanjifan:
I am a fan of Typhoon's rom. Magldr works fine. What is the advantage of cLK?

Thanks.
[HD2 Android NAND Development] icsulescu:
On OP you will find the following answer :

"Q&A

Q: What it is ?

A: A bootloader for android like magldr.

Q: Is it better then magldr ?

A1: NO, it is missing tetris .

A2: NO, magldr has some nice features like partitioning and rmnet.

Q: Can i use last 24MB of nand with this?

A: NO, SPL will erase them. When i have some time i may try to fix it.

Q: Does battery charge with this ?

A: YES, from version 1.3

Q: Does it boot WP7?

A: NO. I am only interested in android but in can load and execute any program.

Q: Should i install it ?

A: If you had to ask probably not. If has no functional benefits over magldr."

But why don't you see for yourself which are the benefits. Personal experience is quite important.

Regards,

Me
[HD2 Android NAND Development] stirkac:
extract zImage from kernel zip and init from typhoon zip(both in boot directory) to some place where you have fastboot. then just do "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz" in cmd in that dir.

cmd command is taken form ali's kernel thread
[HD2 Android NAND Development] mattfmartin:
Ahh ok thanks
[HD2 Android NAND Development] karendar:
The best cLK features are: Fastboot mode, off charging (Real, not workaround off charging like magldr), reboot to recovery, ROM manager support... The only thing for me that it's lacking is rmnet, because it's more stable than ppp for me...
[HD2 Android NAND Development] trilu:
hi all,

at the moment i am on typhoons latest rom with clk. My data connection works still fine. The only point - every time i received a call or do a call, my dataconnection exits, but i cant get data's. I have to disable data, enable again and most time data work until the next call.

Is this a known issue and does exist a workarround?

best regards

trilu
[HD2 Android NAND Development] bhilgeman:
It's the nature of the beast with PPP. The only way currently to fix this is to switch back to Magldr which uses Android's native RMNET protocol. Keep watching here though, I believe they will get RMNET working on Clk at some point.