00:06
belcher has quit [Ping timeout: 252 seconds]
00:17
diejuse1 has quit [Ping timeout: 260 seconds]
00:19
belcher has joined #maemo-leste
00:29
diejuse1 has joined #maemo-leste
00:51
conehead has joined #maemo-leste
00:52
conehead has quit [Client Quit]
00:53
conehead has joined #maemo-leste
00:55
conehead has quit [Remote host closed the connection]
01:23
diejuse1 has quit [Quit: Leaving.]
01:47
kvw_5_ has joined #maemo-leste
01:50
cockroach has quit [Quit: leaving]
01:51
kvw_5 has quit [Ping timeout: 268 seconds]
04:03
pagurus has quit [Ping timeout: 240 seconds]
04:05
ikmaak has quit [Read error: Connection reset by peer]
04:08
ikmaak has joined #maemo-leste
05:52
cr4y1 has joined #maemo-leste
06:59
Oksana has quit [Ping timeout: 260 seconds]
07:01
pere has quit [Ping timeout: 260 seconds]
07:01
diejuse1 has joined #maemo-leste
07:03
adc has quit [Remote host closed the connection]
07:15
Oksana has joined #maemo-leste
07:15
diejuse1 has quit [Read error: No route to host]
07:23
adc has joined #maemo-leste
07:27
pere has joined #maemo-leste
07:55
diejuse1 has joined #maemo-leste
08:01
Pali has joined #maemo-leste
08:01
<
diejuse1 >
@Wizzup. Good news. Managed to successfully launch Hildon Desktop with chroot on Android. Internet works for me too. He managed to perfectly use the application to read PDF documents.
08:02
<
parazyd >
oh that's great
08:02
<
parazyd >
How did you manage to do it?
08:02
<
diejuse1 >
However there are things that do not work. For example the X terminal application does not open, neither do the settings.
08:02
<
parazyd >
You could try opening them manually too
08:02
<
parazyd >
osso-xterm, and hildon-control-panel
08:03
<
Entitlement >
diejuse1 - [ hildon-desktop doesn't render correctly (#70) · Issues · Lima / mesa · GitLab ]
08:04
<
diejuse1 >
DISPLAY=:0 CLUTTER_BACKEND=x11 HD_NOTHREADS=yes CLUTTER_DRIVER=gles2 hildon-desktop.launch
08:04
<
diejuse1 >
did the trick
08:06
<
diejuse1 >
osso-xterm doesn't work either launching it manually
08:06
<
diejuse1 >
But I have installed Xterm, Terminator terminals and working well
08:07
<
parazyd >
I'm sorry I can't help more, but I don't have any kind of rooted Android to try this out
08:07
<
buZz >
what error does 'osso-xterm' give if you start it from a working xterm?
08:07
<
parazyd >
Maybe if you want, you can make a photo or two and I can share it on Twitter
08:07
<
buZz >
did you try 'DISPLAY=:0 CLUTTER_BACKEND=x11 HD_NOTHREADS=yes CLUTTER_DRIVER=gles2 osso-xterm' aswell? :D
08:07
<
diejuse1 >
yesterday I got working Chromium but now is not working. Yesterday works but I couldn't type on search bar
08:08
<
diejuse1 >
Yes buZz. I tried that too. I try many things :-D
08:08
<
diejuse1 >
there is not error
08:08
<
buZz >
so what error does it give
08:08
<
buZz >
when started in a terminal there's no error?
08:08
<
diejuse1 >
no error
08:09
<
parazyd >
There is also osso-xterm.launch, but not sure if that'll change anything
08:09
<
diejuse1 >
i am going
08:09
<
parazyd >
buZz: GPS now works on the N900 btw.
08:09
<
parazyd >
Finished it at 4AM
08:09
<
parazyd >
diejuse1: Nice!
08:09
<
diejuse1 >
osso-xterm.launch works
08:10
<
parazyd >
Good to know
08:10
<
diejuse1 >
How can I view an app in desktop when I install it?
08:10
<
parazyd >
Do you have the Debian icon there?
08:10
<
diejuse1 >
I want chromium, firefox icon
08:11
<
diejuse1 >
No, Debias is not here
08:11
<
parazyd >
That chroot tarball is
_really_ old
08:11
<
parazyd >
So you'll want to `apt dist-upgrade`
08:11
<
parazyd >
But make a backup before you do it
08:12
<
diejuse1 >
apt dist-upgrade is not upgrading nothing
08:12
<
diejuse1 >
Must I change repos>?
08:12
<
parazyd >
first: apt update
08:12
<
parazyd >
then: apt dist-upgrade
08:13
<
diejuse1 >
yes, but not upgrading
08:13
<
diejuse1 >
I always do first apt update
08:13
<
parazyd >
Yeah maybe the repos should be changed
08:13
<
parazyd >
That changed at some point too
08:13
<
parazyd >
Try editing /etc/apt/sources.list and have this instead of the existing maedevu link:
08:13
<
diejuse1 >
I have "ascii"
08:14
<
Entitlement >
parazyd - [ Directory Index - Maemo Leste ]
08:14
<
parazyd >
If the GPG key is expired, you can get it here:
08:17
<
diejuse1 >
I had problems with the "key", I solved using " deb [trusted=true] ... "
08:17
<
parazyd >
You can add the new one with the command above
08:17
<
diejuse1 >
It is dist-upgrading now. :)
08:17
<
parazyd >
good luck
08:18
<
diejuse1 >
It is wonderful using Maemo on Android phone, It is fast. I hope to be able to run the most things
08:21
<
diejuse1 >
I feel like I am using N900 again hehe
08:21
<
buZz >
did you record a video yet? :D
08:21
<
buZz >
i wanna spam it over twitter
08:22
<
diejuse1 >
I will record the video but when I can boast that almost everything works.
08:28
<
diejuse1 >
I'm curious with a question: I set up IRC to talk about Maemo with you. But why do you use IRC and not a more modern application like Discord?
08:29
<
parazyd >
Nothing wrong with IRC
08:29
<
parazyd >
Most developers are on IRC and it works best for us.
08:30
<
parazyd >
If you need some kind of "modern" client, you can join using matrix or something like that.
08:30
<
diejuse1 >
Good answer. The only thing that I have problems in that the past messages of the channel do not appear when I log in.
08:30
<
buZz >
diejuse1: irc will exist 40 years from now
08:31
<
buZz >
all msgs to #maemo-leste are logged in a txt file
08:31
<
parazyd >
See the channel topic for logs
08:31
<
Entitlement >
parazyd - [ #maemo-leste on 2021-05-04 — irc logs at whitequark.org ]
08:32
<
diejuse1 >
I agree with you. IRC works fine and I like it.
08:32
<
diejuse1 >
thanks for the link, parazyd
08:32
<
parazyd >
You're welcome
08:36
<
diejuse1 >
updating now is stuck with "gconf2"
08:37
<
parazyd >
For how long?
08:37
<
diejuse1 >
5mins, I'll wait a bit to see if the update continues
08:37
<
parazyd >
hmm probably not
08:38
<
Entitlement >
parazyd - [ apt - 'sudo dpkg --configure -a' stuck at 'Setting up gconf2 (3.2.6-0ubuntu2) ..... ]
08:44
<
diejuse1 >
I stopped it but I get "could not open lock file /var/lib/apt/lists/lock - open (126: Required key not available)"
08:44
<
diejuse1 >
when I try "sudo apt update"
08:45
<
parazyd >
Try `apt -f install` now
08:46
<
buZz >
parazyd: is bottom right a bionic?
08:46
<
buZz >
never realized screen was bigger
08:47
<
buZz >
oh, no keyboard
08:47
<
buZz >
nevermind :P
08:47
<
parazyd >
Yeah a few mm
08:48
diejuse11 has joined #maemo-leste
08:49
diejuse1 has quit [Ping timeout: 265 seconds]
09:02
diejuse11 has quit [Read error: Connection reset by peer]
09:35
<
sicelo >
I don't have a use for Leste on android, but please consider a simple Wiki write up diejuse1
09:35
<
sicelo >
parazyd: I don't think you need rooted phone :-)
09:39
<
Wizzup >
ascii repos are really old - do we not have newer generic tarballs?
09:41
<
parazyd >
Basically the Paspberry Oi images can be used for a generic approach.
09:43
<
Wizzup >
we might want to indicate that somehow
09:49
<
buZz >
well, maybe wiser to make newer generic tarballs then aswell?
09:49
uvos has joined #maemo-leste
09:50
<
parazyd >
The generic tarball is a raspberry pi image
09:50
<
parazyd >
The problem is that tarballs never could boot when extracted on an sdcard, for reasons unknown.
09:50
<
parazyd >
I rewrote the build system to use cpio archives instead
09:51
<
parazyd >
But in this case it's just redundant to archive and publish both
09:51
<
uvos >
he also needs to get maemo launcher going, when he upgrades from acsii most of the .launch binarys wills stop working
09:56
uvos has quit [Quit: uvos]
10:04
<
Entitlement >
mighty17 - [ android_kernel_ti_omap4/board-espresso-pmic.c at 3.4/common · Unlegacy-Android/a... ]
10:04
<
mighty17 >
that is for vmmc2 (probably in twl6030)
10:05
<
Wizzup >
yeah, upgrading from ascii doesn't seem like a fruitful path to me
10:06
<
freemangordon >
is there an issue with running maemo-launcher?
10:09
<
buZz >
freemangordon: from a chroot on android ;)
10:10
<
freemangordon >
yes, why not?
10:11
<
Wizzup >
I don't think there necessarily is one, diejuse just needs to start it
10:11
<
Wizzup >
openrc should be able to run in chroots, too
10:24
uvos has joined #maemo-leste
10:58
<
Entitlement >
uvos - [ fbkeyboard/fbkeyboard.init at b2ec80e465150dad413c21c852876ab2be8b6e2e · maemo-l... ]
11:24
xes has quit [Ping timeout: 240 seconds]
11:26
<
Wizzup >
missing quote?
11:29
<
uvos >
yeah he accidentaly introduced that
11:30
<
uvos >
since i forgot to change the name :P
11:34
cockroach has joined #maemo-leste
12:27
<
parazyd >
uvos: Fixed, ty
12:27
<
parazyd >
bbl, going to go catch some sun
12:44
pagurus has joined #maemo-leste
13:15
inky has quit [Ping timeout: 260 seconds]
13:26
xmn has quit [Quit: ZZZzzz…]
13:32
inky has joined #maemo-leste
14:24
inky has quit [Ping timeout: 252 seconds]
14:27
inky has joined #maemo-leste
14:29
vectis_ has quit [Ping timeout: 260 seconds]
14:37
pere has quit [Ping timeout: 252 seconds]
14:59
sunshavi has quit [Ping timeout: 252 seconds]
15:01
sunshavi has joined #maemo-leste
15:25
diejuse1 has joined #maemo-leste
15:43
jonsger has joined #maemo-leste
16:05
<
diejuse1 >
Hello all people. I am having many problems after "upgrade" from ascii. I am trying to solve them.
16:11
<
diejuse1 >
hildon-desktop.launch is missing now
16:12
<
diejuse1 >
maemo-launcher doesn't work
16:12
<
uvos >
please be more specific
16:12
<
uvos >
yeah .launch will not work anymore
16:12
<
uvos >
they should still be there tho
16:13
<
diejuse1 >
it has dissparead
16:13
<
uvos >
you upgrade must have remove packages
16:13
<
diejuse1 >
dissapeard
16:14
<
uvos >
hildon-desktop: /usr/bin/hildon-desktop.launch
16:14
<
uvos >
that package contains it if its gohne you need to install it again
16:14
<
diejuse1 >
any idea to launch now? if not, I will downgrade.
16:14
<
uvos >
by installing hildon-meta
16:14
<
uvos >
you must use maemo-launcher/maemo-invoker
16:15
<
uvos >
look at the init script
16:15
<
uvos >
in /etc/init.d
16:17
inky has quit [Read error: Connection reset by peer]
16:19
<
diejuse1 >
apt-install hildon-meta?
16:19
<
diejuse1 >
"unable to locate package"
16:25
<
tmlind >
mighty17: yeah drivers/regulator/twl-regulator.c provides vmmc2
16:26
<
mighty17 >
so use `ti,twl4030-vmmc2` for compatible right? also is that the correct way (ie doing how the board file shows it)
16:27
<
tmlind >
mighty17: no in your board dts, just use &vmmc2, grep for some examples
16:27
<
mighty17 >
n900 has vmmc2
16:28
<
uvos >
did you ever try the usb initiated boot with sysfs masked in kconfig as you suggested, i havent found the time.
16:29
<
tmlind >
mighty: oh but i think vmmc2 is only on twl4030, your link shows your mmc2 is a gpio-regulator
16:29
<
mighty17 >
@tmlind omap4 doesnt seem to have it
16:29
<
tmlind >
mighty17: grep for regulator-gpio
16:30
<
mighty17 >
oh so i need to define vmmc2 in my dts
16:31
<
Wizzup >
diejuse1: I would recommend trying to not upgrade from ascii, and just start with beowulf
16:31
pere has joined #maemo-leste
16:31
<
Entitlement >
mighty17 - [ Ubuntu Pastebin ]
16:32
<
tmlind >
mighty17: hmm maybe compatible = "regulator-fixed" with the gpio pin configured is the way to go nowadays
16:32
<
diejuse1 >
Wizzup. In ascii, I didn't show debian apps like Chromium into desktop. Can I show them?
16:32
<
tmlind >
mighty17: but yeah something like that should work
16:33
<
Wizzup >
diejuse1: yes, all of this is taken care off in beowulf
16:33
<
Wizzup >
do you need armhf or aarch64?
16:33
<
mighty17 >
ohk so i already have it like u said with "regulator-fixed"
16:33
<
mighty17 >
anyway i can know if its working
16:35
inky has joined #maemo-leste
16:35
<
Wizzup >
diejuse1: ok, so can you not use the raspi image as parazyd suggested, or is the problem that you need a tar?
16:35
<
tmlind >
mighty17: you also have to configure your emmc instance to use that regulator
16:35
<
mighty17 >
how do i do that?
16:36
<
diejuse1 >
I am using arm64-generic image
16:38
<
Entitlement >
uvos - [ Directory Index - Maemo Leste ]
16:38
<
uvos >
if your android kernel has loop
16:38
<
uvos >
you should be able to just mount the image and chroot to it
16:39
<
uvos >
then you start the init scripts in /etc/runlevels/default
16:39
<
uvos >
should work in therory
16:40
<
uvos >
maybe grep for export DISPLAY
16:40
<
uvos >
becuse some the scripts assume :0
16:40
<
tmlind >
mighty17: if emmc is mmc2, add &mmc2 entry to your board dts, then configure vmmc-supply = <&your_fixed_regulator_name>; grep for similar examples
16:40
<
mighty17 >
yes i already did that (its for sdcard not emmc xD)
16:40
<
diejuse1 >
uvos, I will try with that image
16:41
<
Entitlement >
mighty17 - [ Ubuntu Pastebin ]
16:41
<
mighty17 >
still it doesnt show up in lsblk and nothing in dmesg
16:41
<
diejuse1 >
uvos, is that image in .tar? it is easier to manage with android
16:42
<
uvos >
no thats why i said to loop mount it
16:47
<
Wizzup >
diejuse1: sorry, meeting atm, back in a bit
16:49
<
Entitlement >
mighty17 - [ Ubuntu Pastebin ]
16:50
<
uvos >
mighty17: your sure you have the right mmc controller right?
16:50
<
uvos >
also a sdcard dosent have a bus-wdith of 8
16:51
<
Entitlement >
mighty17 - [ android_kernel_ti_omap4/board-espresso-sdio.c at 3.4/common · Unlegacy-Android/a... ]
16:51
<
mighty17 >
mighty17: your sure you have the right mmc controller right? umm do i need to enable some config for that?
16:52
<
uvos >
no you need to know how the device is physicaly wired
16:52
<
uvos >
looks like .mmc =2 is the sdcard
16:52
<
uvos >
MMC_CAP_UHS_DDR50 is 4bit data at 50mhz
16:53
<
uvos >
thats a sdcard
16:53
<
uvos >
and bus-width must be 4
16:53
<
uvos >
for your dts
16:53
<
uvos >
on the sdcard mmc controller
16:54
<
uvos >
8bit is emmc
16:54
<
mighty17 >
no mmc2 is non removable and thus emmc/internal memory
16:54
<
mighty17 >
and mmc1 is sdcard
16:54
<
mighty17 >
<uvos "and bus-width must be 4"> it says `.caps= MMC_CAP_8_BIT_DATA,` so im confused
16:55
<
uvos >
well i have no idea how espresso_mmc_info is applyed in the vendor kernelk
16:55
<
uvos >
but the .mmc= 2, entry is the sdcard
16:55
<
uvos >
and its capabilitys are MMC_CAP_8_BIT_DATA and MMC_CAP_UHS_DDR50
16:56
<
mighty17 >
how did u conclude that
16:56
<
mighty17 >
ok what do u mean by sdcard
16:56
<
mighty17 >
the micro sd right? small things that u put in a device
16:56
<
uvos >
because if MMC_CAP_8_BIT_DATA dose what is says
16:56
<
uvos >
it cant be connected to a sdcard
16:56
<
uvos >
because a sdcard just fundamentaly only has 4 pins
16:57
<
uvos >
and mmc =2 has MMC_CAP_UHS_DDR50 as a capability
16:57
<
mighty17 >
yeah so i will put 4 in bus width
16:57
<
uvos >
and thats 4bits at 50mhz
16:57
<
uvos >
whitch is a valid sdcard spec
16:57
<
mighty17 >
but mmc =2 is internal storage
16:59
<
mighty17 >
and it is `.nonremovable = true,` thus confirming it to be internal storage
17:00
<
uvos >
and idk how the vendor kernel processes that sruct
17:00
<
mighty17 >
so it has to be mmc=1 for sdcard
17:00
<
uvos >
but that dosent jibe with 8bit data
17:00
<
uvos >
maybe it just means it can be 8bits idk
17:00
<
mighty17 >
maybe they wrote it wrong
17:00
<
mighty17 >
its downstream after all
17:01
<
uvos >
anyhow in your mainline dts sdcard has 4bit bus width
17:01
<
uvos >
and see if its detected
17:03
<
mighty17 >
Sure will do that
17:18
<
diejuse1 >
uvos, I need the tar file. Mount and unmount a file image has less performance and worse integration with Android
17:21
diejuse1 has left #maemo-leste [#maemo-leste]
17:24
xmn has joined #maemo-leste
17:27
diejuse1 has joined #maemo-leste
17:28
<
Entitlement >
mighty17 - [ Ubuntu Pastebin ]
17:28
diejuse1 has left #maemo-leste [#maemo-leste]
17:37
diejuse1 has joined #maemo-leste
17:43
diejuse1 has quit [Read error: Connection reset by peer]
17:46
diejuse1 has joined #maemo-leste
17:53
diejuse1 has quit [Ping timeout: 265 seconds]
17:57
<
parazyd >
diejuse1: Try mounting the image on your computer and copy it to your phone. There are two partitions in the image, and you should be interested in the second one.
18:01
<
uvos >
diejuse1: use kpartx to split the file into partitons you can mount seperatly
18:05
<
parazyd >
(or partx)
18:13
diejuse1 has joined #maemo-leste
18:17
<
sicelo >
parazyd: weird about the buffer overflow. Didn't happen for me when I played with GPS some months ago
18:24
<
Entitlement >
parazyd - [ gps-nokia-n900: Investigate buffer overflow · Issue #527 · maemo-leste/bugtracke... ]
18:25
<
parazyd >
Note that I also rewrote the Makefile to take dpkg's compiler flags.
18:25
<
parazyd >
So this was probably just never discovered?
18:29
<
sicelo >
I was just compiling the c file. Didn't use the packaging
18:30
<
sicelo >
Anyway, I would have loved to try this out, but the n900 with working modem is the one with broken USB :-p
18:32
diejuse1 has quit [Read error: Connection reset by peer]
18:35
<
parazyd >
Charge a battery in another one and replace? :p
18:36
cr4y1 has quit [Ping timeout: 240 seconds]
18:36
<
parazyd >
I mean, I compiled it in our repos without hardening, so GPS works.
18:37
<
parazyd >
So this is probably not a real priority to fix.
18:37
<
parazyd >
Though if someone wants to take the time, they'd be more than welcome to :)
18:40
cr4y1 has joined #maemo-leste
18:41
diejuse1 has joined #maemo-leste
18:52
diejuse1 has quit [Read error: Connection reset by peer]
18:54
diejuse1 has joined #maemo-leste
18:56
xes has joined #maemo-leste
18:58
<
Wizzup >
parazyd: I think we will see random runtime failures if we don't fix it
18:58
halftux has joined #maemo-leste
18:58
<
Wizzup >
sorry, crazy day atm
19:01
diejuse1 has quit [Read error: Connection reset by peer]
19:03
diejuse1 has joined #maemo-leste
19:05
<
parazyd >
Wizzup: Perhaps. It happens on a specific line in the cod, which is only called once, upon setup of the program, AFAICT. It overflows
_every_ time and aborts if compiled with hardedning.
19:06
<
parazyd >
Without hardening it passes, and I haven't noticed issues so far.
19:07
xes has quit [Quit: bye..]
19:08
<
parazyd >
There are also other compiler warnings which might be good to fix/avoid.
19:08
<
uvos >
it overflows every time?
19:08
<
uvos >
um thats not ok
19:10
xes has joined #maemo-leste
19:10
<
uvos >
so this application translates some random nokia specific format into nema or what dose it do?
19:11
diejuse1 has quit [Read error: Connection reset by peer]
19:11
xes has quit [Client Quit]
19:11
cr4y1 has quit [Ping timeout: 260 seconds]
19:15
diejuse1 has joined #maemo-leste
19:15
xes has joined #maemo-leste
19:16
cr4y1 has joined #maemo-leste
19:21
vectis_ has joined #maemo-leste
19:21
cr4y1 has quit [Ping timeout: 246 seconds]
19:25
<
uvos >
you know what would be cool
19:25
<
uvos >
if the location status widged showed if there where any gpsd clients active
19:25
<
uvos >
isntead of liblocation applications
19:26
<
uvos >
that way navit and sutch would trigger it
19:27
diejuse1 has quit [Read error: Connection reset by peer]
19:30
<
parazyd >
I'm not sure libgps offers such functionality.
19:30
<
uvos >
it could check if the gps backend is open :P
19:31
diejuse1 has joined #maemo-leste
19:34
<
parazyd >
Something to keep in mind :)
19:35
<
uvos >
im kinda shocked that there seams to be no way of asking gpsd
19:35
<
uvos >
but i gues you could listen for gpsd on dbus
19:35
<
uvos >
and if its sending stuff its active
19:35
<
parazyd >
It's not ideal really
19:35
<
parazyd >
I disabled the dbus export on gpsd
19:36
<
parazyd >
And location-daemon uses libgps
19:54
diejuse1 has quit [Read error: Connection reset by peer]
20:00
* enyc
recalls much fun with gpsd on rpi's and stuff
20:00
<
enyc >
the fun of serial converters all with generic id and stuff
20:02
<
Entitlement >
parazyd - [ jpeg (2048 x 1536) ]
20:03
<
uvos >
theres a pinephone missing in that pic :P
20:03
<
uvos >
for a "full" family portrait
20:03
<
parazyd >
uvos: Mine broke :(
20:04
<
parazyd >
Waiting for that hw keyboard before I order a new one
20:04
<
uvos >
thats pretty bad for our pinephone support
20:04
<
uvos >
dose anyone still rune a pp regularly?
20:05
mrgeanie has joined #maemo-leste
20:07
<
parazyd >
Wizzup has both a pinephone and pinetab at home
20:07
pagurus has quit [Remote host closed the connection]
20:08
<
uvos >
why could you not break a bionic or something, they are cheap as chips :P
20:09
<
parazyd >
Yeah, it was on a lab psu and something bad happened
20:09
cr4y1 has joined #maemo-leste
20:10
<
parazyd >
It just stopped drawing current overnight
20:10
<
parazyd >
(PSU is confirmed ok)
20:11
<
uvos >
did you have a power outage
20:11
<
uvos >
some psus ahve some overshoot when turing back on
20:11
<
parazyd >
Not that I remember
20:11
<
uvos >
maybe check its behavior if you have a scope
20:11
<
parazyd >
But yeah I'm suspecting the phone is just frie
20:11
<
parazyd >
I don't unfortunately, but I could find one
20:12
<
parazyd >
To borrow
20:12
<
uvos >
might be worth it, if you want to have some peace of mind if you plan to power the d4 or whatever with it
20:15
diejuse1 has joined #maemo-leste
20:18
diejuse1 has quit [Read error: Connection reset by peer]
20:27
diejuse1 has joined #maemo-leste
20:27
diejuse1 has quit [Read error: Connection reset by peer]
20:31
diejuse1 has joined #maemo-leste
20:31
diejuse1 has quit [Read error: Connection reset by peer]
20:36
diejuse1 has joined #maemo-leste
20:37
xmn has quit [Read error: Connection reset by peer]
20:39
diejuse1 has quit [Read error: Connection reset by peer]
20:39
<
sicelo >
Mmm, my droid4 suddenly won't get past kexecboot after last update (over the weekend?)
20:40
<
sicelo >
Oh, booted now, after 6 boot loops or so
20:40
<
sicelo >
Guess its the USB shenanigans?
20:40
<
uvos >
kexec can also randomly just fail
20:40
<
uvos >
its a bug in the motorola kernel
20:41
<
uvos >
i dont think anyone knows why exactly
20:41
<
uvos >
booting with usb plugged in also has known problems on the mainline side
20:42
<
sicelo >
Okay. At least if it's known issue. I think I can live with it
20:44
<
parazyd >
fwiw a cable without data pins is useful to charge/boot.
20:46
<
sicelo >
I will fix my Nokia charger soon (has shorted data pins. Seems equally effective)
20:47
<
parazyd >
Yeah should be the same result.
20:48
diejuse1 has joined #maemo-leste
20:48
<
uvos >
we could also disable the kernel console on serial for d4
20:48
<
uvos >
except some special kexeboot entry for debuging
20:48
<
uvos >
that should fix all issues, according to my current understanding of the problem
20:50
<
uvos >
(with also the interupt throtteling patch from tmlind)
20:50
<
parazyd >
Can we do it also only for emergency mode?
20:51
<
Wizzup >
uvos: does the location status applet work for you?
20:51
pagurus has joined #maemo-leste
20:51
<
Wizzup >
like, if you press the button in the status context menu?
20:51
<
sicelo >
parazyd: Installing maep has error with /opt/maep/diskcache_check.sh ... guess it should actually be removed
20:51
<
uvos >
Wizzup: yes if currently nothing is using gps
20:51
<
Wizzup >
ok, for me it just hard segfaults
20:51
<
uvos >
Wizzup: no it crashes the status menu if something IS using gps
20:52
<
Wizzup >
sounds like there are a few things to be debugged
20:52
<
uvos >
not sure what its supposed to do when gps is active
20:52
<
parazyd >
sicelo: I didn't do much for maep besides a few quick hacks to get it to compile.
20:52
<
uvos >
when its not it shows the settings dialog
20:52
<
parazyd >
uvos: It should always open the cp applet.
20:53
diejuse1 has quit [Read error: Connection reset by peer]
20:57
<
sicelo >
Mmm, no status menu icon for location showing up on mine so far. Maep open, and, I hope, searching
20:57
<
uvos >
afaik its not installed by default
20:57
<
uvos >
i had to compile it even
20:57
<
uvos >
wasent in repos
20:58
<
sicelo >
Btw ctrl bksp not working now. What was the fix?
20:59
<
uvos >
i forgot to push this to leste config
20:59
<
uvos >
sorry sicelo sec
21:01
<
uvos >
sicelo: your talking about n900 right?
21:01
<
uvos >
replaced by the home key
21:01
<
sicelo >
I want to restore it. What file do I adjust
21:02
<
uvos >
/usr/share/hildon-desktop/shortcuts.ini
21:02
<
uvos >
the left button action
21:02
<
uvos >
note this breaks the home key
21:02
<
uvos >
cant have both atm
21:02
<
sicelo >
I don't need home key, thanks
21:05
diejuse1 has joined #maemo-leste
21:06
<
uvos >
not sure why you would prefer the akward key combination over a dedicated key
21:06
diejuse1 has quit [Client Quit]
21:06
<
uvos >
i did forget to push that ^^^
22:09
halftux has quit [Quit: leaving]
22:10
xmn has joined #maemo-leste
22:17
trench has quit [Ping timeout: 258 seconds]
22:20
jonsger has quit [Ping timeout: 260 seconds]
23:22
sunshavi has quit [Read error: Connection reset by peer]
23:23
sunshavi has joined #maemo-leste
23:25
cr4y1 has quit [Ping timeout: 240 seconds]
23:32
uvos has quit [Ping timeout: 252 seconds]
23:32
<
Wizzup >
parazyd: the location applet on fremantle would say 'coarse accuracy' or 'fine accuracy' I think in the status menu
23:32
<
Wizzup >
ours doesn't say anything currently
23:33
<
Wizzup >
I don't know what the accuracy was based on
23:33
Oksana has quit [Remote host closed the connection]
23:35
Oksana has joined #maemo-leste
23:54
Pali has quit [Ping timeout: 268 seconds]