<SuperMarioSF66>
I guess I won't need more than that. Maybe I will consider just disable that stock android entry.
<uvos__>
you can install leste to the partitions of stock android
<uvos__>
but its a manual procedure atm
<SuperMarioSF66>
at least that is an option.
<SuperMarioSF66>
but I would like to have a unified experience and a lots of storage.So currently I will use SD card. easy for me to do full backups.
<SuperMarioSF66>
I just ordered some MLC based SD card, to serve this usage.
<SuperMarioSF66>
So after I installed on my current SD card, there will be a data moving action taken after I received my extra durance MLC cards.
Pali has quit [Ping timeout: 268 seconds]
<SuperMarioSF66>
and they are berrer performance one too, A2 standard supported, though I doubt that will work on such a old device.
<uvos__>
the sdcard bus runs at 50Mhz Sdr max
<uvos__>
with 4 bit width
<uvos__>
or 8bit for the internal storage
<uvos__>
you can patch it to run at 100Mhz Sdr
<uvos__>
but this is an overclock (that i do run)
<SuperMarioSF66>
I won't take that risk...
<uvos__>
so yeah it can do A2 speeds in this case
<uvos__>
its not a risk to the device
<uvos__>
its supports this speed
<uvos__>
the problem is it uses 5v signaling at 100mhz
<uvos__>
and sdcard spec is 5v at 50mhz or 1.8v at 100
<uvos__>
so you might break the sdcard, but the device is fine
<SuperMarioSF66>
so it requied a newer card to respect 5V signaling?
<uvos__>
no
<uvos__>
no sdcards support 5v signaling at 100mhz
<uvos__>
its not supported by the sdcard spec
<uvos__>
it is used by emmcs tho
<uvos__>
this is why the d4's chip can do this mode
<uvos__>
in reality every sdcard i ever tried had no problem doing 5v @100
<SuperMarioSF66>
so if I can get some eMMC wired there with a special PCB, that will work?
<uvos__>
sure
<uvos__>
but it would be kinda strange for a sdcard to support 5v @50 and 1.8v @100 but break at 5v @100
<uvos__>
so in reallity it allways works anyhow
<SuperMarioSF66>
no worries
<uvos__>
(5v @50 is requried by spec)
<SuperMarioSF66>
I make a backup and I have many spare cards available. even fried one won't a proble,.
<SuperMarioSF66>
*wont be a problem
<uvos__>
anyhow for now yes stock kernel dosent do a2 speed
<SuperMarioSF66>
I guess that card won't work because they were formatted with ext4 to begin with...
<uvos__>
your dding a filesystem
<uvos__>
what it was formated as is immaterial
<SuperMarioSF66>
I mean... stock android won't just work on ext4
<uvos__>
oh no
<SuperMarioSF66>
for SD card at least
<uvos__>
it cant mount modern ext4 at all
<uvos__>
it needs disabled csums
<SuperMarioSF66>
blazing fast 30+MB/s dding
dev has left #maemo-leste [Disconnected: closed]
<SuperMarioSF66>
oh I was wrong, it just a decompression. actual DD speed is 80MB/s+
SuperMarioSF66 has quit [Ping timeout: 252 seconds]
xmn_ has quit [Remote host closed the connection]
xmn has joined #maemo-leste
SuperMarioSF has quit [Quit: Client closed]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
oh I'm back. seems RevolutionIRC client had some bugs and I can't connect to libera.chat properly.
<Wizzup>
wb
SuperMarioSF has quit [Ping timeout: 244 seconds]
SuperMarioSF has joined #maemo-leste
SuperMarioSF has quit [Ping timeout: 268 seconds]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
Got my sim card
Livio has joined #maemo-leste
<SuperMarioSF>
works just fine, however signal isn't very good on UMTS.
<SuperMarioSF>
seems that LTE only works with CDMA side.
SuperMarioSF has quit [Ping timeout: 252 seconds]
dev has joined #maemo-leste
<Wizzup>
yeah
<uvos__>
LTE is unrelated to CDMA but supports one band
<uvos__>
13 iirc
<uvos__>
and on leste it dosent work at al
<uvos__>
since we dont power the LTE modem and dont have a driver for it
Livio has quit [Ping timeout: 252 seconds]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
OK I'm back, downloading files for flashing.
<SuperMarioSF>
Done, I'm in.
<SuperMarioSF>
Looks like there is no UI for 3G right now.
<SuperMarioSF>
is there a way to enable that in commandline?
<SuperMarioSF>
or should I install modemmanager or something to manage?
<uvos__>
theres a ui that might sorta work in -devel
<uvos__>
but it dosent at all for me (and installing it breaks all conectivity for me)
<uvos__>
for others it dose work
<uvos__>
theres a metapackage called hildon-connectivity-mobile or some sutch
<SuperMarioSF>
so how can I install that -devel?
<uvos__>
otherwise you have to use qmi-cli
<SuperMarioSF>
a package or whole image?
<uvos__>
please read the documentation, its in the wiki under development
<SuperMarioSF>
OK
<Wizzup>
let me know if doc is hard to find, can try to help, but I'm travelling right now, so might be in and out
SuperMarioSF has quit [Quit: Client closed]
SuperMarioSF has joined #maemo-leste
<SuperMarioSF>
I found the doc and enabled devel repos
<SuperMarioSF>
so just a dist-upgrade next?
<SuperMarioSF>
btw I can provide some i18n work for Chinese.
<SuperMarioSF>
and already working on it on weblate.
<Wizzup>
there are also meta pkgs you need, I can't look it up right now
<SuperMarioSF>
any hint for that meta package?
<Wizzup>
SuperMarioSF: let me look now
<Wizzup>
SuperMarioSF: hildon-connectivity-mobile at least
<Wizzup>
you will still need to do -some- manual steps after boot, depending on whether you sim has a pin or not
<SuperMarioSF>
I removed PIN for my SIM card before using in d4.
<Wizzup>
ok
<Wizzup>
in that case, install that package and reboot, see how far it gets you :)
<SuperMarioSF>
so should I finish the dist-upgrade first (downloaded)
<Wizzup>
yeah, sure, do that too
<SuperMarioSF>
woah that's a lot packages...
<Wizzup>
lots of translations too I bet
<SuperMarioSF>
actually, Simplified Chinese doesn't have much translation unfinished...
<SuperMarioSF>
the majority of them is just city names.
<Wizzup>
:)
<Wizzup>
that is only for the core of course
<Wizzup>
user contributed packages and such might need more
<SuperMarioSF>
OK
<SuperMarioSF>
I have purchase PoEdit Pro so that shouldn't be very hard.
<SuperMarioSF>
rebooted.
<Wizzup>
do you see a sim not present icon, or does the status menu look the same?
<Wizzup>
the modem ought to get online'd once you go to internet connections through the tsatus bar
<Wizzup>
(where you also search for wifi)
<Wizzup>
it might take a bit for the d4 to first make a connection I suppose
<SuperMarioSF>
it is booting...
<Wizzup>
(btw since ofono mostly talks over dbus, I usually use dbus to debug it's states, but iirc there are also some scripts (ofono-scripts pkg?)
<SuperMarioSF>
btw a suggestion, please make some LED on during a power cycle, or that will be diffcult to know my device is still powering down or not.
<uvos__>
this exits on power down
<uvos__>
and works
<SuperMarioSF>
Oh, a SIM card icon shown, however looks like it doesn't find my SIM card.
<uvos__>
but only if you shutdown with something other than the terminal
<Wizzup>
SuperMarioSF: ok, give it a little bit of time (1-2 mins)
<Wizzup>
the modem itself doesn't report on sim status until then
<Wizzup>
it's possible you will see the sim missing icon disappear soon
<SuperMarioSF>
and desktop wallpaper is gone
<uvos__>
uh
<Wizzup>
huh?
<SuperMarioSF>
attempt to set a new wallpaper, got error: No space left
<uvos__>
oh
<Wizzup>
oh...
<uvos__>
you need to expand the partiton before upgrade
<Wizzup>
/etc/expandcard.sh will resiez the sd card
<SuperMarioSF>
and sim icon gone.
<SuperMarioSF>
oh
<uvos__>
you broke your install now :/
<SuperMarioSF>
I forgot that
<Wizzup>
I hope the apt-get dist-upgrade worked fully
<SuperMarioSF>
time to reinstall
<Wizzup>
uvos__: not sure if it's broken?
<Wizzup>
apt usually errors on disk full
<uvos__>
yeah when i did that last weak it broke it
<SuperMarioSF>
dist-upgrade and that package successfully completed.
<Wizzup>
and then you can resume it manually
<uvos__>
but maybe he is lucky
<uvos__>
[13:12] <Wizzup> apt usually errors on disk full
<uvos__>
for some reason that is farily unreliable
<SuperMarioSF>
resizing
<uvos__>
i have this problem on other machines too
<SuperMarioSF>
OK, done, reboot?
<uvos__>
yeah hopefully it will be ok
<SuperMarioSF>
no worries, I can just reinstall from start.
<uvos__>
we could maybe make the image a couple 100mb larger
<uvos__>
so that devel fits
<Wizzup>
yeah.
<SuperMarioSF>
the interesting thing is there is no error reported during upgrade and install.
<Wizzup>
we try to make it work for very small cards
<Wizzup>
SuperMarioSF: yeah probably you were just on the edge
<SuperMarioSF>
the space is barely enough
<SuperMarioSF>
Ok
<SuperMarioSF>
everything is back
<SuperMarioSF>
SIM icon show no card.
<Wizzup>
give it a minute again :)
<SuperMarioSF>
and icon is gone...
<Wizzup>
we probe and power the modem relatively late in the boot process, and the modem needs time to start up itself
<Wizzup>
ok, that means your sim is found, likely
<SuperMarioSF>
nothing left except battery icon
<SuperMarioSF>
so what's next?
<uvos__>
wait
<uvos__>
should come up with a signal
<Wizzup>
uvos__: no, it will only online the modem in the network search dialog
<SuperMarioSF>
is there are debug logs to see here?
<uvos__>
right true
<Wizzup>
you can install ofono-scripts and run stuff like /usr/share/ofono/scripts/list-modems
<Wizzup>
or use dbus if you know it
<SuperMarioSF>
oh
<SuperMarioSF>
singal shown
<Wizzup>
but if you just go to the place where in maemo you usually connect to a network, just opening the dialog will make it online the modem
<SuperMarioSF>
uhh... there is a problem
<uvos__>
right heres where mine never works beyond this point
<SuperMarioSF>
connection selection was grey out
<SuperMarioSF>
everything cannot be selected.
<uvos__>
right same here :)
<uvos__>
wait a bit
<uvos__>
its wating for ofono to provision the net
<uvos__>
but it never happens here
<SuperMarioSF>
OK
<Wizzup>
and for the modem to become online
<SuperMarioSF>
I can see signal but it is weak (1 bar)
<SuperMarioSF>
started from 3 bars
<Wizzup>
that's good, 2g or 3g?
<Wizzup>
that means the modem is online
<uvos__>
the signal bars are very conservative on d4
<SuperMarioSF>
no technology were displayed. only bars.
<Wizzup>
so -probably- you can even make a phone call now with sphone
<Wizzup>
SuperMarioSF: huh, that's ie
<Wizzup>
that's weird
<SuperMarioSF>
sphone stucked at dialing
<SuperMarioSF>
and it closed itself
<Wizzup>
stuck how?
<SuperMarioSF>
stuck, not means freeze.
<Wizzup>
so I am wondering if this is actually using some tech that we have not mapped :)
<Wizzup>
if you see bars but no icon
<uvos__>
check what ofono thinks tech is
<uvos__>
in list-modems
<SuperMarioSF>
and there is a problem
<SuperMarioSF>
WiFi cannot be connected...
<Wizzup>
slow down :D
<uvos__>
right if mobile network dosent work the applet breaks wifi
<Wizzup>
uvos__: not for me :/
<uvos__>
because it hangs icd forever
<Wizzup>
icd doesn't hang, the dialog waits for something
<SuperMarioSF>
if there is a way to let me get a usb0 interface via USB?
<uvos__>
right the dialog hangs
<Wizzup>
SuperMarioSF: just plug in usb and it'll show up
<SuperMarioSF>
seems my Windows machine need a driver.
<Wizzup>
I don't know how it works on windows
<Wizzup>
sorry
<SuperMarioSF>
I'm backing to home, and I will attempt connect that to my Mikrotik router.
<Wizzup>
do you have a linux device?
<SuperMarioSF>
I do know how to make it work after that.
<uvos__>
probubly no one here runs windows on pcs :P
<Wizzup>
so I'm wondering what the technology here will be
<uvos__>
if you want wifi to work again, just unstiall the mobile icd applet
<Wizzup>
uvos__: list-modems doesn't show it fwiw
<uvos__>
(for now)
<SuperMarioSF>
I have linux based device at home, but I don't want to setup the connection manually, so I will use a router instead. ( I know how to do that)
<Wizzup>
ok
<uvos__>
Wizzup: you can see it in ofono-scipts for sure
<uvos__>
Wizzup: i gues maybe not that one
<SuperMarioSF>
oh wait
<Wizzup>
uvos__: yeah I was searching
<SuperMarioSF>
wifi just came back on itself
<uvos__>
right autoconnect works
<uvos__>
same here
<Wizzup>
do we have a ticket for this behaviour?
<uvos__>
pretty sure i made one
<SuperMarioSF>
btw there are some suggested package during install hildon-connectivity-mobile, so maybe something missing can be in there?
<Wizzup>
this is the gconf entry for my KPN 3g data
<Wizzup>
it was generated automatically
<Wizzup>
(the ips get updated in there)
<Wizzup>
the part after IAP/ is just a uuid
<Wizzup>
so ideally you'd have something like that, but clearly it is not there
<SuperMarioSF>
so i should replace the data with my own?
<Wizzup>
not sure if it will work
<Wizzup>
I am wondering, what is the second context that you are seeing?
<Wizzup>
you said there were two
<SuperMarioSF>
usually we have two profile in China. one is 3gnet for internet access. one is 3gwap for ISP proxied access.
<SuperMarioSF>
same applied to all 3 ISPs in China.
<Wizzup>
ok
<Wizzup>
uvos__: do you have more than one context?
<SuperMarioSF>
btw, usually the XXwap one also act as the network that MMS works on.
<Wizzup>
SuperMarioSF: if you know how to write gconf data (it's painful, you have to do it per value and specify the type etc) it might be worth a shot to create an entry like mine, but it's not a great way
<uvos__>
Wizzup: my d4 is 100km away
<Wizzup>
uvos__: :)
<uvos__>
buut
<SuperMarioSF>
maybe I should make a script to do that automatically
<Wizzup>
you went outside without a leste device in your pocket? shame :D
<uvos__>
sorry :(
<Wizzup>
SuperMarioSF: well, we have code to do it automatically, we need to fix our code :)
<uvos__>
but its in my network at home, maybe i can ssh in :P
<Wizzup>
SuperMarioSF: so, there might log entries in /var/log/maemo/icd2.log that could be helpful
<SuperMarioSF>
ok let me connect to wifi
<uvos__>
heh i can
<uvos__>
Wizzup: can i check what you need over ssh only?
<SuperMarioSF>
and I'm unable. ICD UI constantly say network error. (and that was a public open wifi)
<Wizzup>
SuperMarioSF: there might be something like this: SIM %s seen for the very first time, provisioning.
<Wizzup>
uvos__: yes, via mdbus2
<Wizzup>
SuperMarioSF: hm, wifi doesn't fail for me often, but usually on retry it works for sure
<uvos__>
im gona have to enable the modem via scripts (cant interact with icd gui ofc
<uvos__>
)
<Wizzup>
I can give you mdbus2 commands for it
<uvos__>
ok
<Wizzup>
SuperMarioSF: actually all the logs that are relevant will be prefixed with [OFONO]
<sicelo>
RE: space issues ... maybe we really should auto-run expandcard on first boot
<SuperMarioSF>
searched that file, doesn't contain either 'SIM' nor 'seen'. something went wrong.
<Wizzup>
sicelo: hm, yeah..
<Wizzup>
SuperMarioSF: what about 'ofono' ?
<uvos__>
./list-modems "Technology = gsm"
<uvos__>
Wizzup: it dose show there
<uvos__>
for me at least
<Wizzup>
uvos__: so just run this: mdbus2 -s org.ofono
<Wizzup>
uvos__: and then see how many /motmdm_0/context* stuff you see
<SuperMarioSF>
nope, not even for 'ofono#
<SuperMarioSF>
* 'ofono'
<Wizzup>
SuperMarioSF: what does dpkg -L libicd-network-ofono say?
<Wizzup>
SuperMarioSF: (fwiw in case you did a case sensitive search, it's OFONO in the logs)
<SuperMarioSF>
listed its file in that package.
<uvos__>
Wizzup: zero
<Wizzup>
SuperMarioSF: hm, ok.
<SuperMarioSF>
upper case tried, no result.
<uvos__>
just /motmdm_0/operator
<Wizzup>
I suppose libicd-network-ofono has to be loaded on your system, because it onlines the modem for you
<Wizzup>
uvos__: hm, with the modem online and pin provided etc?
<uvos__>
yeah
<Wizzup>
uvos__: ok that's weird
<Wizzup>
uvos__: we can debug that later I suppoes, normally ofono auto creates a context
<uvos__>
( both done via scripts, i can try to reboot and try via icd over dbus if you can give me commands)
<Wizzup>
nah won't matter I think
<SuperMarioSF>
so ICD doesn't care about usb0 interface?
<Wizzup>
nah
<SuperMarioSF>
ok
<SuperMarioSF>
I can setup a port forward and make the phone SSH on internet or ZeroTier.
<SuperMarioSF>
if you need to debug it will be there.
<Wizzup>
mdbus2 -s org.ofono /motmdm_0/context1 org.ofono.ConnectionContext.SetProperty Active true
<Wizzup>
or it will block until it times out unless you kick ofono in the meantime :P
<uvos__>
returned sucess instantly
<Wizzup>
uvos__: does it show as active now?
<uvos__>
yeah i got a ip and everything
<Wizzup>
SuperMarioSF: btw, super glad to hear that that calls worked for you, that cost us a lot of time to get mostly working
<Wizzup>
uvos__: ok, so I guess for you also the gprs provisioning in our ui is the problem
<SuperMarioSF>
yeah, call and sms is a tricky thing to work with.
<uvos__>
would be a neat fix - maybe the d4 would be closer than 100km if that would work ;P
<uvos__>
*neat to fix
<Wizzup>
SuperMarioSF: just to be clear there are still some problems with our ofono
<SuperMarioSF>
I was playing some full feature LTE modem device before. Setup for a call with only serial ttys are painful...
<Wizzup>
like I sometimes repeatedly 'receive' the same sms on my d4
<uvos__>
SuperMarioSF: on droid 4 its relatviely easy - the d4 implements everything in hw
<uvos__>
like you can issue a call and shutdown linux
<uvos__>
call will continue
<Wizzup>
will be harder to hang up :P
<uvos__>
still yeah was plenty work
<uvos__>
Wizzup: well the other party has to hang up then :P
<SuperMarioSF>
or wait until battery dies...
<sicelo>
the modem will power the speakers?
<uvos__>
cpcap contains all the hw to drive the spekers, and you gave the channels to the modem, so yes
<uvos__>
if you shutdown linux but dont change cpcap reg state
<uvos__>
the call would work
<uvos__>
cpcap also handles the some of the audio procesing, other processing is handled by the modem
<uvos__>
the cpu dose nothing
<Wizzup>
bbl
<SuperMarioSF>
reminds me about some early Windows Mobile phones. They don't have 'Airplane mode', they have 'Phone Power Down' mode, and that just disable modem alright.
<SuperMarioSF>
maybe if Windows Mobile freezes the call should just go on.
<sicelo>
otoh, it scares me ... because now it means the modem/cpcap have a life of their own. such setup really absolutely needs kill switches
<uvos__>
sicelo: no
<uvos__>
sicelo: since the modem can not talk to cpcap at all
<uvos__>
sicelo: it only has analog audio connections to it
<uvos__>
sicelo: so it cant give itself the speaker or the mic
<uvos__>
sicelo: on xt860 thats the end of it
<SuperMarioSF>
so I guess if hacker got your modem hacked, the only thing they can do is rickroll you. (x)
<uvos__>
on d4 the lte modem DOSE have access to cpacap and could control its registers
<uvos__>
but it dosent have a audio interface
<uvos__>
so the only way something nefarious could happen is if the lte modem and the qcom modem comunicated over the internet
<uvos__>
and the lte modem gave the qcom modem the mic and speakers
<uvos__>
fiarly absurd thret model
<uvos__>
also the lte modem is not powered in leste
<uvos__>
ofc all modems have gps and the tower knows roughtly where the modem is anyhow
<uvos__>
so the modem alone can be nafarious enough
<sicelo>
especially when it can be doing things with cpcap behind linux' back
<SuperMarioSF>
no wonder I know some people who make DIY phones doesn't have celluar network at all, they use LoRA instead.
<uvos__>
sicelo: as state this is impossible on leste
<uvos__>
*stated
<uvos__>
unless you use a gpio hack to power up the lte modem
<uvos__>
(from linux)
<uvos__>
if your concerned about that run xt860 i gues
<SuperMarioSF>
if there is a way to bridge some joint point to do that?
<sicelo>
i don't know how much one can trust cpcap to begin with, as "cpcap contains all the hw to drive the spekers, and you gave the channels to the modem, so yes"
vagag has joined #maemo-leste
<uvos__>
if you expect cpcap to have some kind of hw level surveilnce then you might as well assume omap4 also has soemthing like that
<uvos__>
omap4 also has pelty of microcode you could hide something in
SuperMarioSF has quit [Quit: Quit]
<sicelo>
i know
<sicelo>
i didn't know there were additional places to hide it :p
SuperMarioSF has joined #maemo-leste
bh has joined #maemo-leste
lexik has joined #maemo-leste
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 252 seconds]
SuperMarioSF has quit [Remote host closed the connection]
SuperMarioSF has joined #maemo-leste
<buZz>
Wizzup: i do feel isp autoconfig needs some hard work
<buZz>
my sim was roaming in .be and .lu recently, finally saw 3G again, but couldnt get data working over it :(
SuperMarioSF has quit [Ping timeout: 252 seconds]
SuperMarioSF has joined #maemo-leste
<sicelo>
i forgot - are we using mobile-broadband-something-info? if we are, maybe you can add your connection profiles to it. they're very accepting upstream. at least i added mine without issues
SuperMarioSF has quit [Remote host closed the connection]
SuperMarioSF has joined #maemo-leste
SuperMarioSF has quit [Remote host closed the connection]
SuperMarioSF has joined #maemo-leste
uvos__ has joined #maemo-leste
uvos has joined #maemo-leste
<uvos>
maybe just figure out what android dose and use that (maybe only as fallback)
<uvos>
its guaneteed to work everywhere since operators have great incentive
<norayr>
> then theres a boot menu with entries you can edit via a text file, by default theres 2 entries, leste from sd and stock android from /system
<norayr>
> uvos__ wrote:
<norayr>
> but you can have as many entries as you want
<norayr>
So i didn't understand can we have an entry which just gets charge? or we should use console maemo option in hope it'll be enough power to boot until charge started?
SuperMarioSF has quit [Ping timeout: 252 seconds]
<norayr>
we moved we should move again soon. so i did not unpack most of the boxes and i don't know where is my generic battery charger. But i was abloe to disassemble another charger for canon batteries
<uvos>
if you boot with usb plugged in it the nromal leste entry should enter charge mode
<uvos>
it dosent at least for sicleo
<uvos>
but yeah
<uvos>
other than that
<norayr>
and keep droid's battery several minutes with those contacts
<uvos>
the stock android option is the quickest
<uvos>
and will enter androids charge mode
<norayr>
and it was enough for it to boot to console leste and start taking charge. but i was not able to use ih for several days before
<norayr>
now it gets charge
<uvos>
so really the d4 should never get into the state where it cant boot all the way to leste anyhow
<uvos>
since we have leste shutdown early to prevent it
<uvos>
on low bat
<uvos>
so unless you messed with the values or you battery is in very poor state or you leave the device unantended for multiple weaks while off and empty
<uvos>
it should not happen
<norayr>
SuperMarioSF: congrats, having droid is fun and you already have fun with it
<uvos>
booting to console leste should be about the same as booting to charge mode
<uvos>
except the backlight will be on
<uvos>
so its worse
<norayr>
oh
<uvos>
otherwise its the same (kernel and sysinit userspace have to boot before we can start charging)
<norayr>
in my experience booting to leste console mode is faster and therefore more chances to start booting
<uvos>
charge mode skips more parts
<norayr>
it takes 0.6 amper in this state
<uvos>
so its impossible for it to be faster
<uvos>
they both boot the same kernel and the sysinit runlevel
<norayr>
androids charge mode didn't help me...
<uvos>
and then console mode boots another runlevel
<uvos>
if androids charge mode dosent work
<uvos>
this strongly suggests android dosent like the battery
<norayr>
it was drawing 0.1-0.2 amper for whole night, then
<norayr>
it was warm in the morning
<norayr>
but was not able to boot.
<norayr>
even a bit
<norayr>
yes android doesnt like most of my batteries
SuperMarioSF has joined #maemo-leste
<norayr>
but droid3 is so beautiful
<SuperMarioSF>
OK I'm back
<SuperMarioSF>
I'm at home
<SuperMarioSF>
and ready for port forwarding
<norayr>
alas its maemo boots and shuts down severl minutes later
<norayr>
but even near sony xperia it looks sooo cool
<uvos>
norayr: yeah so if android dosent charge your batteries while in charge mode that suggests hw failure or at least that android thinks charging is unsafe
<norayr>
unlike droid4
<norayr>
it did chalge the battery it came with
<uvos>
it checks way more parameters than we do
<norayr>
but that battery was in bad shape
<uvos>
it checks temperature deltaT and deltaV
<uvos>
to ensure its safe
<norayr>
very interesting
<uvos>
(at least)
<SuperMarioSF>
btw I have a Sony Ericsson SK17i
<SuperMarioSF>
very tiny yet powerful phone
<SuperMarioSF>
ok my tmate session created.
<buZz>
SuperMarioSF: need some help with d4 gprs?
<SuperMarioSF>
yup
<buZz>
whats up
<SuperMarioSF>
that why I am creating tmate session
<buZz>
whats a tmate?
<SuperMarioSF>
a terminal share service, via SSH or web terminal
<buZz>
ah, multiplayer ssh? screen -x
<SuperMarioSF>
yup
<buZz>
'connecting to gprs' for me on d4 causes all other networks to disconnect, btw
<sicelo>
btw, RE: provisioning - at least with networks in my country, i've had to manually add apn. android has never auto-provisioned them
<sicelo>
of course, there's an USSD code one can dial, where operator sends the phone a configuration message. i think ofono knows how to handle those
<SuperMarioSF>
the link provided are Web based terminal and SSH connection, for both read-only and read-write types.
<sicelo>
so for my networks, i guess mobile-broadband-provider-info is more useful than built-in mechanisms
* sicelo
installs a trojan on SuperMarioSF's phone :-D
<SuperMarioSF>
oh, I am monitoring the session of course.
<SuperMarioSF>
since this session is provided to help you guys pinpointing the issue, if something went wrong, I can just reinstall, or replace with a new phone if needed.
<sicelo>
what problem are you troubleshooting btw?
<SuperMarioSF>
things working are: calling, SMS
<SuperMarioSF>
problem is: ICD unable to provision connection profile properly
<SuperMarioSF>
ofono knows what APN my ISP provides.
<SuperMarioSF>
mdbus2 was installed.
<SuperMarioSF>
the password are defaults, so therefor this session is inside a tmate, not a internet facing SSH connection.
<SuperMarioSF>
to prevent restarting ICD cause connection termination, the SSH link to d4 is over USB RNDIS
<SuperMarioSF>
and that USB connected to my router.
<SuperMarioSF>
everything just works.
<SuperMarioSF>
oh btw a question
<SuperMarioSF>
how can I type ":" and ";" with d4 hardware keyboard?
<uvos>
ok+:
<SuperMarioSF>
I almost can't quit vim because I have no idea how to type them.
<uvos>
see wiki
<SuperMarioSF>
oh i missed that one
Livio has joined #maemo-leste
Pali has joined #maemo-leste
<SuperMarioSF>
since no one actually joined the SSH session, I'm closing it.
<Wizzup>
SuperMarioSF: sorry, I was literally running to make my connecting flight
<Wizzup>
we can do this remote debug another day?
<SuperMarioSF>
sure
<SuperMarioSF>
when you have time just mail me if i'm not online.
<Wizzup>
alright
<SuperMarioSF>
usually I'm online at 02:00 ~ 16:00 UTC
<Wizzup>
for me that is 0800 - 0100 utc
<SuperMarioSF>
plenty overlap, that's ok
<SuperMarioSF>
if you can do debug work tomorrow, I will leave my d4 at home connected to router, so I can setup connection remotely for you.
<SuperMarioSF>
it will be connected via usb0 so restart icd won't be an issue.
<SuperMarioSF>
and I just test, it can even survive a reboot.
<Wizzup>
alright, sweet
<SuperMarioSF>
hmmmm not excatly
<Wizzup>
reboot can take a few mins
<SuperMarioSF>
seems reboot caused my router not picking the device.
<SuperMarioSF>
however I can reset the USB on router so maybe it will work again.
<SuperMarioSF>
I'm testing this
<SuperMarioSF>
there are some known issue with RouterOS based devices on RNDIS interface. that is one of it.
<SuperMarioSF>
usually need to reset USB port once to get it working.
<SuperMarioSF>
sometimes this may get even worse, it won't pick up any RNDIS interface, and you have to bring a real Android to enable RNDIS on it once, then it will happily accept any RNDIS devices afterwards.
<SuperMarioSF>
oops
<SuperMarioSF>
I have some bad news
<SuperMarioSF>
seems it can't reset itself via USB hub
<SuperMarioSF>
a powered hub
<SuperMarioSF>
Time to add more things to make it happen.
<SuperMarioSF>
I'm adding a smart switch.
<SuperMarioSF>
OK it worked, finally
<Wizzup>
you could run the gadget in local.d as well
ashley has quit [Quit: Whatever.]
<SuperMarioSF>
I guess the problem is without a power reset on USB, gadget won't be working properly after reboot.
<SuperMarioSF>
so I add a smart switch to solve the issue, and it worked,
<Wizzup>
ok
<SuperMarioSF>
just send USB bus reset on router, following with a power cycle on Hub's power, everything will be back online.
<SuperMarioSF>
btw maybe customizing device vendor info will be nice. currently it was Foo Inc Bar Device.
<SuperMarioSF>
better be: Maemo Leste Fundation Droid 4 Device. ;P
ashley has joined #maemo-leste
ashley is now known as Guest2751
<SuperMarioSF>
* typo: Foundation
SuperMarioSF has quit [Quit: Client closed]
SuperMarioSF has joined #maemo-leste
<Wizzup>
SuperMarioSF: actually I set that to foo and bar :)
<Wizzup>
buZz: this also fails on my n900 and other phones
<Wizzup>
it's probably unrelated to leste specifically
<buZz>
now we just need to write a PC suite? :D
<Wizzup>
other operators here work
<buZz>
hehe
<Wizzup>
pc suite is pretty easy, the modem access of it not so much
<buZz>
unless we abuse usbgadget for it?
<buZz>
i think that can emulate a serial port anyway, we could just 1:1 pass it through with a small tool
<freemangordon1>
Wizzup: you are in BG?
<buZz>
(i dont know what pc suite all did)
<uvos>
why do we want modem access thrugh pc suite?
<buZz>
no clue
<buZz>
i do love the idea of connecting a droid4 to my laptop for 'internet access' with USB
<uvos>
well you dont need direct access to the modem for that
<buZz>
but usb ethernet gadget thingy can be used for that, i think
<uvos>
usbnet and some routing
<buZz>
yeah
<freemangordon1>
uvos: oh, seems you have fixed the auto-relock thingie (at least judging by mce changelog)
<buZz>
probably even better without
<Wizzup>
freemangordon1: yup, just now
<uvos>
freemangordon1: yes but its a stop gap
freemangordon1 has quit [Quit: Leaving.]
<buZz>
Wizzup: thats always such a weird idea in my head, if we are 'maemo 7' why are we just trying to be 1:1 'maemo 5'
freemangordon has joined #maemo-leste
<Wizzup>
buZz: hm?
<uvos>
i still need to rewirte the input layer to use libinput
<buZz>
i mean, many things in UI are done away with 'thats how fremantle did it'
<buZz>
etc
<Wizzup>
buZz: this isn't about UI
<Wizzup>
it's about modem func
<Wizzup>
and the sim + this operator is just weird
<buZz>
100% of my sims have that experience
<freemangordon>
never had any issue abroad
<uvos>
so that it can share device share configureation with xorg/sdl/wayland (think callibration, ignored devices, what is a gamepad/mouse/ts/etc)
<freemangordon>
besides most of the places now have disable 3G
<buZz>
i'm gonna buy a second gprs capable sim just for testing mosh powerusage btw, gonna look for a provider that allows me just a 1 month contract
<Wizzup>
freemangordon: this is about kpn (dutch) with vivatel/vivacom specificallu
<Wizzup>
buZz: cool
<freemangordon>
Wizzup: yeah
<buZz>
shouldnt cost me >10 eu , i -expect-
<Wizzup>
uvos: libinput as opposed to, /dev/input/ ?
<buZz>
maybe i can put a usb charger connected to that d4 with a sonoff so i can turn charging on/off remotely
<uvos>
Wizzup: right atm it just opens all the event devices itself and reads them
<Wizzup>
I mean, it's a pretty sane way, no? :)
<uvos>
no
<Wizzup>
what's lacking?
<Wizzup>
just curious
<uvos>
because not all input devices should be used, and callibration should be applied and mce should not have its own heuristics of what is a mouse/keyboard/gamepad etc
<uvos>
libinput uses udev hints and has a huge list of exceptions that makes it work reliably
<uvos>
mce cant compeat
<uvos>
also we configure xorg via libinput (callibration - ignoreing some stuff)
<uvos>
mce needs its own special config to do the same thing - again.
<Wizzup>
ah ok, that makes sense, so it's for properties and such
<uvos>
yes
<buZz>
you can have some intelligence about which type of /dev/input/event devices to try
<buZz>
like by bus
<buZz>
or something
<uvos>
righ libinput dose all these things
<uvos>
and has a large exception table to fix where things go wrong
<uvos>
and can be configured via udev rules
<uvos>
and that then applies to xorg/wayland/sdl etc
<uvos>
all in one place
<sicelo>
uvos: re - modem via 'pc suite' ... usbnet + routing is difficult for the average user, while handling (AT) modems is very easy even in OSes such as Windows
<uvos>
sicelo: we cant really assume every phones modem is goning to have a at interface
<uvos>
sicelo: so this means implementing a modem emulator
<uvos>
android presents a usbnic, that seams best
<uvos>
and is easy to deal with on windows too
<sicelo>
hence i added AT in () ... the point is - this stuff is seamless in almost any OS, unlike messing with usb-net. have you ever seen how RNDIS stuff works in Windows?
<sicelo>
anyway ...
<uvos>
sure its a bit of a mess
<uvos>
still better than routing out the raw modem imo
<uvos>
btw mbm can do this iirc
<uvos>
on d4
<uvos>
cpcap can directly route the modem out to the usb port
<sicelo>
cpcap :-)
<uvos>
not a fan of the chip eh? :P
<sicelo>
buZz: tbh, leste was never really going to be maemo '7' in that sense. it was simply 7 because 6 was already taken by Harmattan. Otherwise, it was always going to be based largely on Fremantle. at least in the beginning
<buZz>
sicelo: right, sure, i can understand it from starting point, just not from dailydriver + 'we have the wheel' standpoint, always ;)
<sicelo>
maybe it'll end up like iOS ;-)
Livio has quit [Ping timeout: 268 seconds]
<buZz>
sicelo: taking screenshots of programs so you dont see the recovery from swap?
mardy has quit [Quit: WeeChat 2.8]
<sicelo>
that too
<buZz>
:)
<buZz>
i kinda like the live thumbnails in app switcher
<buZz>
or whatever its called
<sicelo>
others don't
<sicelo>
the nature of people :-)
<buZz>
i have no idea, i barely used smartphones ever since wince/symbian wasnt a thing anymore ;)
<uvos>
i like it, i just dont think its worth it resource wise.
<buZz>
the live thumbs arent worth it?
<uvos>
no
<buZz>
does it eat a lot of ram?
<uvos>
they force a extra full screen buffer of eatch app at all times
<buZz>
or resources? i havent noticed much cpu load from it
<uvos>
(even when not in the switcher)
<buZz>
but didnt look at power stats specifically
<buZz>
gee
<uvos>
also they eat a lot of ram bandwith
<uvos>
= a lot of power
<buZz>
maybe we can change that behaviour to use caches more efficiently?
<buZz>
s/caches/buffers/
<uvos>
not really
<uvos>
you could suspend compositing when not in the switcher
<uvos>
but this requires lots of rearchitectureing in hildon
<sicelo>
buZz: sometimes i miss S80 (found in the Communicators, 9500/9300). Apparently that's where Hildon traces its roots from
<buZz>
i think we could do 'better' for the future ppl that use leste once its 'gamma'
<sicelo>
sure :-)
vagag has left #maemo-leste [#maemo-leste]
<sicelo>
btw, of late, when my d4 manages to get into charge mode, it gets stuck there. only a hard reset allows me to get to a working system
<Wizzup>
new kernel problem?
<uvos>
no this is the drm hang
<uvos>
charging sdl gets into the same drm hang as xorg
<Wizzup>
in the ioctl
<Wizzup>
?
<uvos>
yeah
<uvos>
it uses blocking io so its a little different
<uvos>
but yes essentally
dev has left #maemo-leste [Disconnected: closed]
Danct12 has quit [Read error: Connection reset by peer]
<norayr>
buzz, i also love it. i am ready to pay resources for it.
<norayr>
and i do, i have many pidgin windows opened on maemo always
<buZz>
:D with moving video inside?
<norayr>
and pidgin with many many windows eats less resources than one dino with one window
<norayr>
well in pidgin i see that text is updated, and scrolled
<norayr>
i see some changes in 'watch' command outputs in remote ssh sessions
<norayr>
or i connect to one or two console chat servers. com, if u heard.
<norayr>
i hate it that phosh is so slow, eats so much memory on the same device, and shows screenshots
<norayr>
it's so dumb for me
<norayr>
also they have one line of windows in phosh
<norayr>
so i need to scroll through all to choose the window i need
<norayr>
in maemo it's there after one or two taps
<norayr>
i can see it
<norayr>
maemo is very fash aand lightweight
<norayr>
it is fast on droid
<norayr>
i guess on n900, didn't try
<norayr>
and on pinephone it is probably a fastest distro
<norayr>
if we don't count bad video driver
<norayr>
which already improved a lot
<norayr>
you know, i was working on very old and slow machines
<norayr>
for we droid or pinephone aren't weak
<norayr>
but very powerful
<norayr>
so we can afford it
<norayr>
also it can be implemented more efficdently
<norayr>
after all on xorg screen we see many windows simultaneously with updates in them
<norayr>
could be maybe something like thatmto save resources
<norayr>
still with all its 'hunger' leste is the fastest and most responsive intelfare imo.
<norayr>
and it makes sense. it was written long ago and didn't get much wmore hunger since.
<norayr>
i don't know why on such a powerful device like pinephone i should wait for so long fol simple gtk3 or qt programs to start. i even afraid tht maybe that's gtk3 problem.
<norayr>
and what do they do in dino that it draaains so much power?
<norayr>
pidgin with 29 opened windows can be opened whole day for me
<norayr>
20
<norayr>
plus live wallpaper
<norayr>
in wy desktop life i always use windowmaker.
<norayr>
i was using 486 with linux, it had troubles playing mp3 files. i was giving high priority to the special fork of mpg123 for 486 in order to be able to liten music.
<norayr>
and since long ago i am in lovu with wmaker. it takes like 2mb in ram. and it is extremely flexible.
<norayr>
i don't know what i am talking about
<norayr>
probably that i think phosh and praasma are toooo fatty
<norayr>
and waemo is so responsive i don't feel it is slow on very old and 'weak' devices.
<norayr>
but those aren't weak.
<norayr>
for someone who started vith com'uher with 32kb of ram
<norayr>
it is a miracle.
<norayr>
and i think gnome3 and kde plasma obviously do something wrong if they are so slow on pinephone.
<norayr>
and dino, that it drains the battery ten times faster than pidgin with tens of opened windows.