Release Telegram

ingoreis · Jan 17, 2016

This Time it use /dev/adsp but do not work again.
I will try to reflash now here and use a clean card for better Test.

AL lib: (EE) ALCcaptureOSS_open: Could not open /dev/adsp: Device or resource busy

edit:
-reflashed
-reupdated the OS
-deleted the old Appdata complete

and do not work either the Microphone

Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
AL lib: (EE) ALCcaptureOSS_open: Could not open /dev/adsp: Device or resource busy

ptitSeb · Jan 17, 2016

@ingoreis, redownload the version again, I think you don't have the latest one. And then remove the appdata/telegram/.alsoftrc before launching it.

ingoreis · Jan 17, 2016

@ptitSeb
Thats right i had the wrong Version

now this Error:
AL lib: (EE) ALCcaptureAlsa_open: snd_pcm_hw_params_set_rate(self->pcmHandle, hp, device->Frequency, 0) failed: Invalid argument

sorry for the bad News from me.

ptitSeb · Jan 17, 2016

Ok. Do you have sound with the last version? If yes, I'll put it on the repo.
I still cannot reproduce the error, so I don't think I'll find a workaround anytime soon.

ingoreis · Jan 17, 2016

One Version before worked better because when i now try to record Sound then Telegram will not play Voice Messages now.
Your OSS Version seem to work better than the Alsa Version.

ptitSeb · Jan 17, 2016

So, I have put the "oss" version on the repo.

I'll probably not find a workaround (I'm not a user of that software, I don't reproduce the problem on my pandora). So do not hesistate to play with the file ".alsoftrc" (in apddata/telegram/home) and maybe also ".soundrc" (to be created) and if someone succeed in getting both audio playback and capture, send me the parameters for updating the PND.

Build 05
-----------

Updated to latest 0.9.19 git sources
Still issue with the sound (plays ok but can't record).

ingoreis · Jan 17, 2016

And Animated Gif support now..many Thx for your hard Work on this.
I love Telegram and my Brother Kevin too

Eight Bit · Mar 17, 2016

I have a question about this, when using Telegram, I can't play any music, eventhough I'm just typing messages and switched off audio in the Telegram settings. What can I do to fix this so that I can continue using my Open Pandora normally when Telegram is running?

Thanks!
8

Silent-Hunter · Apr 10, 2016

Eight Bit said:
I have a question about this, when using Telegram, I can't play any music, eventhough I'm just typing messages and switched off audio in the Telegram settings. What can I do to fix this so that I can continue using my Open Pandora normally when Telegram is running?

Thanks!
8

I second this. No other app can play sound, so if someone sends me a youtube link on Telegram I can't hear it.

ptitSeb · Apr 10, 2016

Problem with Telegram is that it oupen Alsa for sound Output & Input, using mono for sound input. It doesn't quite work for now.
@KickAss has sent me some alsa config to try fix that (I was testing with UltrastarDX), maybe you can try:
create a file named ".asoundrc" inside appdata/telegram/home and fill it

Code:

# Output + Input config for ptitSeb v0.2 (avoiding dmix)
# This is the hardware enabled ALSA config file.
# It is meant to set audio output to hardware (built in speakers and mic).

pcm.mic {
    type plug
    slave {
        pcm "plughw:0,1"
        channels 1
        rate 44100
    }
}

pcm.speakers {
    type plug
    slave {
         pcm "hw:0"
         rate 44100
    }
}

pcm.softvol {
    type softvol
    slave {
          pcm "speakers"
    }
    control {
          name "Master"
          card 0
    }
}

pcm.!default {
    type asym
    playback.pcm {
        type plug
        slave.pcm "softvol"
    }
    capture.pcm {
        type plug
        slave.pcm "mic"
    }
}

Maybe it'll help.

KickAss · Apr 10, 2016

hey,
i just got notified about this issue...
i will look into it eventually

Kosmos · Apr 12, 2016

Ok, so I'm a latecomer on this! Well I try to start it and I get nothing......

appdata/telegram gets created
/mnt/pnd/telegram and /mnt/utmp/telegram also were created. The app does not start though.

From CLI in Root I see that the Start sh Fails!

Any idea?

ptitSeb · Apr 12, 2016

@Kosmos : look at /tmp/pndrun_telegram.out to see if there is something helpfull.
Is your firmware up-to-date?

Kosmos · Apr 12, 2016

Sorry, FW is 1.55

I hope THAT is not the problem because I have been enjoying my setup for a long time. LOL

Here is the tmp/pndrun_telegram.out

=======================================================================================
PND : /media/BOOT/pandora/menu/telegram.pnd
PND_FSTYPE : Squashfs
APPDATADIR : /media/BOOT/pandora/appdata/telegram
APPDD_FSTYPE : vfat
PND_CPUSPEED : <unset>
EXENAME : runscript.sh
ARGUMENTS : <unset>
=======================================================================================
[ START ]--- Mount the PND ----------
mkdir: cannot create directory `/mnt/utmp/telegram': File exists
WARNING Union already mounted, using it
+++++++
Loopback devices :
/dev/loop0: [b301]:87 (/media/BOOT/pandora/menu/Conky_1.9.pnd)
/dev/loop1: [b301]:109 (/media/BOOT/pandora/menu/telegram.pnd)
Are mounted on :
/dev/loop0 on /mnt/utmp/Conky type squashfs (ro,relatime)
/dev/loop1 on /mnt/utmp/telegram type squashfs (ro,relatime)
For these Union :
none on /mnt/utmp/Conky type aufs (rw,relatime,si=bfb4be56,noplink)
none on /mnt/utmp/telegram type aufs (rw,relatime,si=b9ade056,noplink)
[SUCCESS]--- Mount the PND ----------
[ START ]--- Starting the application ( runscript.sh ) ----------
/usr/pandora/scripts/pnd_run.sh: line 523: cd: /mnt/utmp/telegram: Stale NFS file handle
/usr/pandora/scripts/pnd_run.sh: line 551: ./runscript.sh: No such file or directory
[ FAILED]--- Starting the application ( runscript.sh ) ----------
[ START ]--- Restoring the frame buffer status ----------
[SUCCESS]--- Restoring the frame buffer status ----------
[ START ]--- uMount the PND ----------
[ START ]--- Waiting the Union to be available ----------
[SUCCESS]--- Waiting the Union to be available ----------
auplink:auplink.c:59: chdir: Stale NFS file handle
umount: /mnt/utmp/telegram: Stale NFS file handle
auplink:auplink.c:59: chdir: Stale NFS file handle
WARNING umount UNION failed, didnt clean up. Process still using this FS :
+++++++
Loopback devices :
/dev/loop0: [b301]:87 (/media/BOOT/pandora/menu/Conky_1.9.pnd)
/dev/loop1: [b301]:109 (/media/BOOT/pandora/menu/telegram.pnd)
Are mounted on :
/dev/loop0 on /mnt/utmp/Conky type squashfs (ro,relatime)
/dev/loop1 on /mnt/utmp/telegram type squashfs (ro,relatime)
For these Union :
none on /mnt/utmp/Conky type aufs (rw,relatime,si=bfb4be56,noplink)
none on /mnt/utmp/telegram type aufs (rw,relatime,si=b9ade056,noplink)
[SUCCESS]--- uMount the PND ----------
=======================================================================================
Return code is : 3

ptitSeb · Apr 12, 2016

Looks like a corrupted something.
Re-download the PND
Check your SDCard for error.

Kosmos · Apr 12, 2016

ok, I tried redownloading telegram.pnd again on my laptop.... Then I tried on my Pandora in links... Then in Epiphany through PanDebian.... Now am I am trying an older pnd version... Still fail. I guess I just will not be using TG on my Pandora. Here's the new out file from the last attempt.

=======================================================================================
PND : /media/BOOT/pandora/menu/telegram.20150605.064231.pnd
PND_FSTYPE : Squashfs
APPDATADIR : /media/BOOT/pandora/appdata/telegram
APPDD_FSTYPE : vfat
PND_CPUSPEED : <unset>
EXENAME : runscript.sh
ARGUMENTS : <unset>
=======================================================================================
[ START ]--- Mount the PND ----------
mkdir: cannot create directory `/mnt/pnd/telegram': File exists
mkdir: cannot create directory `/mnt/utmp/telegram': File exists
WARNING Union already mounted, using it
+++++++
Loopback devices :
/dev/loop0: [b301]:87 (/media/BOOT/pandora/menu/Conky_1.9.pnd)
/dev/loop1: [b301]:353 (/media/BOOT/pandora/menu/telegram.pnd)
/dev/loop3: [b309]:15 (/media/PANDORA128/pandora/apps/PanDebian_sqsh-Pandora128.pnd)
/dev/loop4: [b309]:244 (/media/PANDORA128/Debian-squeeze)
Are mounted on :
/dev/loop0 on /mnt/utmp/Conky type squashfs (ro,relatime)
/dev/loop1 on /mnt/utmp/telegram type squashfs (ro,relatime)
/dev/loop3 on /mnt/utmp/PanDebian-PanDebian type squashfs (ro,relatime)
/dev/loop4 on /media/ram/PanDebian type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
For these Union :
none on /mnt/utmp/Conky type aufs (rw,relatime,si=eb18020d,noplink)
none on /mnt/utmp/telegram type aufs (rw,relatime,si=eb05fa0d,noplink)
none on /mnt/utmp/PanDebian-PanDebian type aufs (rw,relatime,si=eb2d070d,noplink)
[SUCCESS]--- Mount the PND ----------
[ START ]--- Starting the application ( runscript.sh ) ----------
/usr/pandora/scripts/pnd_run.sh: line 523: cd: /mnt/utmp/telegram: Stale NFS file handle
/usr/pandora/scripts/pnd_run.sh: line 551: ./runscript.sh: No such file or directory
[ FAILED]--- Starting the application ( runscript.sh ) ----------
[ START ]--- Restoring the frame buffer status ----------
[SUCCESS]--- Restoring the frame buffer status ----------
[ START ]--- uMount the PND ----------
[ START ]--- Waiting the Union to be available ----------
[SUCCESS]--- Waiting the Union to be available ----------
auplink:auplink.c:59: chdir: Stale NFS file handle
umount: /mnt/utmp/telegram: Stale NFS file handle
auplink:auplink.c:59: chdir: Stale NFS file handle
WARNING umount UNION failed, didnt clean up. Process still using this FS :
+++++++
Loopback devices :
/dev/loop0: [b301]:87 (/media/BOOT/pandora/menu/Conky_1.9.pnd)
/dev/loop1: [b301]:353 (/media/BOOT/pandora/menu/telegram.pnd)
/dev/loop3: [b309]:15 (/media/PANDORA128/pandora/apps/PanDebian_sqsh-Pandora128.pnd)
/dev/loop4: [b309]:244 (/media/PANDORA128/Debian-squeeze)
Are mounted on :
/dev/loop0 on /mnt/utmp/Conky type squashfs (ro,relatime)
/dev/loop1 on /mnt/utmp/telegram type squashfs (ro,relatime)
/dev/loop3 on /mnt/utmp/PanDebian-PanDebian type squashfs (ro,relatime)
/dev/loop4 on /media/ram/PanDebian type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
For these Union :
none on /mnt/utmp/Conky type aufs (rw,relatime,si=eb18020d,noplink)
none on /mnt/utmp/telegram type aufs (rw,relatime,si=eb05fa0d,noplink)
none on /mnt/utmp/PanDebian-PanDebian type aufs (rw,relatime,si=eb2d070d,noplink)
[SUCCESS]--- uMount the PND ----------
=======================================================================================
Return code is : 5

EPIC FAIL!

ptitSeb · Apr 12, 2016

Same message, and still looks like a corruption or something.
Is you SDCard Fat32and Ext formated?
If Fat32, try to repair it on a windows computer. Or use GParted on the pandora to repair it, but don't put gaparted.pnd on the SDCard you want to repair.

Also, remove te appdata/telegram folder if any.

Kosmos · Apr 12, 2016

Ok, I gparted/Repair'd the SD on my laptop and tried again! You're right..... Now I get an error that seems like a better pointer in the right direction!

[ START ]--- Mount the PND ----------
Mounting : mount -t squashfs -o ro "/dev/loop0" "/mnt/utmp/telegram"
Mounting the Union FS : mount -t aufs -o exec,noplink,dirs="/media/PANDORA128/pandora/appdata/telegram=rw+nolwh":"/mnt/pnd/telegram=rr" none "/mnt/utmp/telegram"
[SUCCESS]--- Mount the PND ----------
[ START ]--- Starting the application ( runscript.sh ) ----------
old version, removing old .alsoftrc if exist
rm: cannot remove `/mnt/utmp/telegram/home/.alsoftrc': No such file or directory
installing default .alsoftrc
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

Does this make more sense; maybe it will provide a solution? Thanks for your time

ptitSeb · Apr 12, 2016

Nope, that Qt error is harmless (it's always there with Qt apps and doesn't prevent them to run).
Does the log end there? or are there more message after that?

Kosmos · Apr 12, 2016

Thats the end. I also tried it from the Nand and it ended there as well.

Release Telegram

Hardcore Member

Serial Porter

Hardcore Member

Serial Porter

Hardcore Member

Serial Porter

Hardcore Member

Hardcore Member

Hardcore Member

Serial Porter

Very Active Member

Member

Serial Porter

Member

Serial Porter

Member

Serial Porter

Member

Serial Porter

Member

Similar threads