<Wizzup>
I will revoke parazyd's access this month
<dsc_>
/win 26
<buZz>
Wizzup: what happened, totally unknown?
<buZz>
hope he's ok
<Wizzup>
norayr: you should be all set
<Wizzup>
buZz: honestly I don't care at this point, I am sure he has had the opportunity to reach out to us
<buZz>
:(
<Wizzup>
I just want my fxtec back
<buZz>
yeah :(
<Wizzup>
norayr: I think you're all set
<buZz>
Wizzup: i remember, back on maemo 4/5 , it was kinda common to see 'alternative kernel builds' as packages in the repos
<buZz>
with overclocking or whatever
<buZz>
maybe i should package a 'EB41 kernel' ? :)
<buZz>
this 15% extra capacity imho is supernice, and seems to work well
<Wizzup>
buZz: no, we shouldn't have additional kernels, we have full control over this
<buZz>
right, ok
<Wizzup>
let's see what your changes are and what uvos and Tony think
<buZz>
they're 'unsafe'
<buZz>
:)
<Wizzup>
this is charging the battery to like 4.35V?
<buZz>
-better- would be getting nvmem functional and actually identifying the batteries
<buZz>
yes
<Wizzup>
yeah we decided not to do it after we all had several droid4's with batteries as balloons
<buZz>
with EB41s ?
<buZz>
or as in, accidentally had the 4.35V charging on a normal lipo that wasnt HV?
<Wizzup>
no, just having it on 4.35V for proloned times seems to really decrease life time of battery
<Wizzup>
brb
<buZz>
oh, right, yeah i assume so, its a battery from 2012 anyway ;)
<buZz>
its on 4.35V for almost no time though :P charging voltage is 4.35V but when it reaches that it almost directly declares 100% and drops to ~4.3V
<buZz>
maybe i can try charging only to 4.31V instead, see what the difference in mAh will be
vgratian has left #maemo-leste [#maemo-leste]
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
<Wizzup>
buZz: right but I often keep my d4 plugged in over night
<Wizzup>
and then suddenly it's 25% of the time (yeah 6 hr sleep :p) on 4.35V
<Wizzup>
in any case, open a pr and we can discuss the best way
<buZz>
gee, well, i'll try 4.31 or 4.3
<buZz>
'best' would be have the kernel identify batterytype, and also actually read charge cycles and temperature
<Wizzup>
norayr: reminder that you have to accept the invite
<buZz>
Wizzup: yeah but afaik its not functional, if you check dmesg you'll see cpcap report that it wasnt able to detect batterytype
<buZz>
at least, i've never seen it work , something about nvmem not working yet? plus preventing something else from working? cant remember exactly. i'll open a issue anyway
<buZz>
Wizzup: oh btw, since my mod, i'm -finally- for the first time able to hit that 'charge mode' we added this year(?) or recently anyway
<buZz>
with the cpcap-charger.c still running 4.2V , it would never do that, with it on 4.35V , it -always- hits it when i boot with USB connected
<buZz>
Wizzup: oh actually, wait, it didnt hit it this boot
<buZz>
might just be the 'power supply connected before power-on, doesnt appear as power supply connected when kernel boots'
<Wizzup>
it depends on the battery state and also on the cable
<buZz>
hm right
<buZz>
but i do think cpcap-charger is somehow involved in how it reads the USB , if it calls it 'lets be charging' or not
<buZz>
which then triggers charge-mode or not
<buZz>
thusfar i havent pinpointed the exact requirements to hit it
norayr has left #maemo-leste [Disconnected: closed]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: Replaced by new connection]
norayr has joined #maemo-leste
<buZz>
i still need to find where that 'battery low at 3.4V! going to shutdown now!' is coming from :P i think that should follow the MIN VOLTAGE of cpcap-battery aswell
<buZz>
or well, with some margin for shutdowntime obviously
<buZz>
is there a way to start the appmanager without it breaking my nonproper gprs connection? :D
<buZz>
btw i've had >48hr connections on gprs now :D
norayr has left #maemo-leste [Disconnected: Replaced by new connection]
norayr has joined #maemo-leste
<Wizzup>
buZz: hm, with ssh or mosh?
<buZz>
yeah mosh running
<buZz>
(really sucks battery though)
<buZz>
often i leave it hooked up to a usb powerbank with 2x 18650
<buZz>
or on external power
<buZz>
so yeah, i'll be monitoring puffyness of battery for sure
<buZz>
maybe i'll redo as 4.3 or 4.31 anyway just to be a bit closer to safety
<Wizzup>
I use ssh, so I think/thought that used a lot more power
<Wizzup>
buZz: didn't mena to scare you, that's just what we found
<buZz>
hehe np , i've been calling my modification 'bermbom' anyway
<Wizzup>
I'd love to try a bionic with uvos' battery choices
<Wizzup>
I feel like I have to charge my d4 a bit too much still
<buZz>
if i can lower that powerdown voltage a bit more, i think i can do ~10hr of screen+mosh on the d4
<buZz>
+gprs, on battery alone
vagag has left #maemo-leste [Error from remote client]
<dsc_>
so telepathy-idle facilitates being online on IRC
<dsc_>
d4 people will have the device in their pants /whatever
<dsc_>
and travel around
<dsc_>
i.e: the device will reconnect all the time
<Wizzup>
yes, unless they connect to a bouncer
<dsc_>
result: IRC channel gets spammed with quit/join
<dsc_>
timeouts*
<Wizzup>
this is inherently an irc problem
<dsc_>
hehe yes
<Wizzup>
we don't need to solve it
<dsc_>
fair
<Wizzup>
there are clients that allow you to use both the ncurses part and also use it as a bouncer -- I think weechat?
<Wizzup>
not sure
<Wizzup>
in any case I'd probably consider the irc use case mostly for testing
<Wizzup>
it's not super likely that avif irc users will keep it connected all the time, also because the protocol doesn't do anything wrt push notifications etc, to save battery
<rafael2k>
Here in Moscow, I never managed to make VoLTE work tbh... but also there is no specific VoLTE profile for MTS
<rafael2k>
but CSFB just works, and the modem automagically switches to 2G or 3G in a voice call
<rafael2k>
I might try beeline just in case... but at some point I'll try the open source firmware for the quectel modem
<rafael2k>
then I'll have some motivation to understand a bit more what is going on when a call goes CSFB or VoLTE
<buZz>
rafael2k: they do on d4 ;)
<buZz>
iirc n900 aswell?
<rafael2k>
the default on PP is not this
<rafael2k>
do you remember the config file to set the actions for the volume buttons?
<rafael2k>
I remember I already changed them to open vkb, do crazy Xorg things, but can not remember its path
<buZz>
ehw, no not really, sorry
vagag has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
<Wizzup>
rafael2k: the bug report mentions it
<Wizzup>
rafael2k: oh, isn't that just hildon or mce?
missMyN900 has joined #maemo-leste
<missMyN900>
uvos: how do you feel about buying a brand new battery for a DB? Is it a good idea or is it better to buy a used one that has actually been charged?
<missMyN900>
after some consideration I have dropped the idea of buying a T100TA; I would rather buy a new/open box DB
<missMyN900>
so yeah I will probably sell my PP and buy a DB
<missMyN900>
DB + HW8X is absolutely massive though; I love it, reminds me of my N900 <3
<norayr>
Wizzup: so i am here, sorry wasn't here. But i understand if it's not convenient anymore.
<missMyN900>
norayr: would you consider backporting elisa as I see you are on a packaging spree again :)?
<missMyN900>
Wizzup: is all that also necessary for DB or only for D3? Sounds very complicated
<rafael2k>
[Shortcuts]
<rafael2k>
RaiseVkb=XF86AudioRaiseVolume
<rafael2k>
LeftButton=XF86AudioLowerVolume
<rafael2k>
but I'm not sure how to make the volume buttons really change the pa volumes...
<Wizzup>
missMyN900: would have to check
<Wizzup>
bbiab
<norayr>
ok the video said tap on four points of the screen and it'll take you to os.
<norayr>
it says 'communicating with server' and there was a rotating wheel
<norayr>
and now connection failed, complete the setup by setting up a wifi etc
<norayr>
let me try to skip it
<norayr>
but do i really really need the os to function?
<norayr>
ok i got it
<norayr>
i got android
<norayr>
minute i'll figure out the version of os
<norayr>
yeah, i was right:
<norayr>
Android 2.3.4
<norayr>
it was 4.something.
<rafael2k>
Wizzup: who should do this automation, mce or hildon or anything else?
<norayr>
i cannot find 'usb debugging' on this android 2. is it there at all? do i need it?
<norayr>
tapping build number in 'about phone' doesn't help.
<norayr>
to bring 'you are a dev'
Twig has quit [Ping timeout: 268 seconds]
<norayr>
i got 'waiting for device' shell i run root234.sh in 'pc mode' or some other mode?
<norayr>
no 'usb debugging' found
<norayr>
no, i can only enter 'usb connection' setting by sliding from up to down and choose from 'pc mode', 'windows media sync', 'usb mass storage', 'charge'.
<norayr>
right now i try 'pc mode'
<norayr>
ok i found allow usb debugging in 'applications'
<norayr>
the root script rebooted the phone
<norayr>
rooted
<norayr>
rebooting second time
<uvos>
missMyN900: no idea really
<uvos>
the only datapoint i have is that the bw8x from 2012! has almost rated capacity (~2000mah versus 2200mah rated)
<uvos>
but i have only one of those
<uvos>
i also have 2 hw4x and 6x eb41 (same cell, different case), all of those have <60% rated capacity left
<norayr>
but i got things like Unable to chmod /system/bin/logwrapper: Read-only file system
<norayr>
is it ok?
<uvos>
no
<norayr>
shell i try to use install.sh in fastboot mode?
<uvos>
no
<uvos>
that cant work
<uvos>
usually if anything goes wrong your screwed
<norayr>
ok booting android again.
<uvos>
you have to reflash the stock android image
<norayr>
i sort of did, not purposefully.
<norayr>
i guess.
<norayr>
somehow.
<norayr>
ok trying again.
<uvos>
please follow the instrcutions extreamly carefully
<uvos>
its very very fagile
<uvos>
and i think your only the 3rd persion to ever do this
<uvos>
after Wizzup and me
<buZz>
22:54:21 < Wizzup> it's just touching the corners clockwise, -I think-
<buZz>
i think that is in docs already?
<uvos>
yes thats correct
<norayr>
buZz: yeah it helped me.
<uvos>
it is for bionic
<buZz>
same on d4
<uvos>
right but you dont need it on d4
<uvos>
you do need it on bionic (if not upgraded to android 4+) and on d3
<buZz>
oh, ok
<uvos>
(to install lexte)
<uvos>
*leste
<uvos>
or los
<uvos>
you would need it to use motorola android, not sure why you would want to over los
<uvos>
:P
<buZz>
welp, its the only android on my droid4's anyway :P
<uvos>
missMyN900: yes the bionic also has a convoluted install process (much better tested than d3 tho)
<uvos>
missMyN900: the d4 is unique in its very easy install process
<uvos>
(honestly easer then even n900's uboot ironicly)
<norayr>
i hope when it says 'prepare sd card' it doesn't do anything to my sdcard with leste.
<buZz>
nope, it doesnt
<uvos>
not unless you touch it
<uvos>
it then lets you do a format
<uvos>
obv thas bad :P
<norayr>
allowed 'unknown sources' and rooting again.
<norayr>
hope it'll help.
<norayr>
not able to boot it to recovery to reset device with vol up+vol down kes
<norayr>
yet
<buZz>
whats the goal?
<norayr>
no still 'unable to chmod'
<norayr>
i don't know i am trying to follow instructions to be able to install kexecboot
<norayr>
to boot leste from sdcard
<missMyN900>
uvos: hmm interesting; thanks for sharing
<buZz>
norayr: then why are you rooting it?
<buZz>
its not really needed for leste, we arent using anything from android