sixkxbeh has quit [Remote host closed the connection]
sixkxbeh has joined #maemo-leste
sixkxbeh has quit [Remote host closed the connection]
<ajr>
Looks like my lucky day.. snagged a brand new d4 from ebay
joerg is now known as _j
_j is now known as jOERG_rw
jOERG_rw is now known as joerg
uvos has quit [Ping timeout: 252 seconds]
diejuse has joined #maemo-leste
joerg has quit [Read error: Connection reset by peer]
joerg has joined #maemo-leste
diejuse has quit [Quit: Leaving.]
elastic_dog has quit [Ping timeout: 268 seconds]
elastic_dog has joined #maemo-leste
sixkxbeh has joined #maemo-leste
sixkxbeh has quit [Ping timeout: 268 seconds]
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daanct12 has joined #maemo-leste
Daaanct12 has quit [Ping timeout: 252 seconds]
BenLand100 has quit [Quit: s/BenLand100//]
<mighty17[m]>
<parazyd "Thanks for considering :)"> Form unavailable:(
<ajr>
Worked for me a couple hours ago, must have closed
<ajr>
looks like a cool project
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
belcher_ has joined #maemo-leste
belcher has quit [Ping timeout: 268 seconds]
DocScrutinizer has joined #maemo-leste
joerg has quit [Killed (copper.libera.chat (Nickname regained by services))]
DocScrutinizer is now known as joerg
lyubov_ has quit [Ping timeout: 264 seconds]
lyubov_ has joined #maemo-leste
<tmlind>
uvos: ok so bad emmc, but still some hope for usable xoom2 allow-mbmloader-flashing-mbm.bin then, i need to at least make a backup of my rootfs before i will try it though
<tmlind>
also what needs to be tested is if booting to recovery and resetting the system also resets the utags partition, i doubt it though, but would allow a way to recover
BenLand100 has quit [Quit: s/BenLand100//]
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
BenLand100 has quit [Quit: s/BenLand100//]
mrkrisprolls has quit [Ping timeout: 244 seconds]
BenLand100 has joined #maemo-leste
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has quit [Quit: s/BenLand100//]
<parazyd>
ajr, mighty17[m]: thanks. Yeah, I guess it's done.
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
BenLand100 has quit [Quit: s/BenLand100//]
BenLand100 has joined #maemo-leste
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has quit [Quit: s/BenLand100//]
sixkxbeh has joined #maemo-leste
sixkxbeh has quit [Remote host closed the connection]
uvos has joined #maemo-leste
<uvos>
parazyd: missed it :(
<parazyd>
No worries :D
<parazyd>
btw. I'll try to compile also 5.10 kernel with the updates and patches today.
<parazyd>
-devel with 5.11 seems fine.
<Wizzup>
ajr: great @ snag :)
<Wizzup>
parazyd: do we have a way to test that 5.10 before it goes out to everyone?
<parazyd>
Not unless we use the same kernel both in devel and stable
<parazyd>
Which we should imo
<Wizzup>
how do we test new kernel versions then?
<Wizzup>
I'm trying to guard against a one time bad build or something that breaks all user devices after upgrade
<parazyd>
We test new versions in devel.
<parazyd>
My point is we would propagate 5.11 to stable (but we cant because of bugs)
<parazyd>
Ideally we go to ddk 1.19 and solve everything
<Wizzup>
mhm
<parazyd>
err 1.17 but you get the point
<uvos>
we could revert to 5.1o in devel
<uvos>
we could revert to 5.10 in devel
<uvos>
and put 5.11 into expieramental
<uvos>
or drop it
<parazyd>
Also a possibility, yes
mrkrisprolls has joined #maemo-leste
Pali has joined #maemo-leste
<mighty17[m]>
uvos: kernel panics, no working init found
<Wizzup>
hard to tell why that would be the case, how did you get the rootfs set up?
<Wizzup>
(really, serial or keyboard would be much easier to debug)
<mighty17[m]>
<Wizzup "hard to tell why that would be t"> rootfs is droid4
<mighty17[m]>
but this device isnt droid4***
<Wizzup>
so you dd'd a droid4 to a sd card and starting modifying it, right?
<Wizzup>
a droid4 image
<mighty17[m]>
yes
<Wizzup>
ok
<Wizzup>
I am not sure if the usbnet service starts when X does not start
BenLand100 has quit [Quit: s/BenLand100//]
inky has quit [Ping timeout: 272 seconds]
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
BenLand100 has joined #maemo-leste
<mighty17[m]>
ohk, well where can i upload a vid of simplefb logs
inky has joined #maemo-leste
BenLand100 has quit [Quit: s/BenLand100//]
BenLand100 has joined #maemo-leste
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
diejuse has joined #maemo-leste
BenLand100 has quit [Quit: s/BenLand100//]
BenLand100 has joined #maemo-leste
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daanct12 has joined #maemo-leste
Danct12 has quit [Ping timeout: 252 seconds]
Pali has quit [Ping timeout: 272 seconds]
diejuse has quit [Quit: Leaving.]
Daaanct12 has joined #maemo-leste
Daaanct12 has quit [Changing host]
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 245 seconds]
inky has quit [Ping timeout: 272 seconds]
sixkxbeh has joined #maemo-leste
sixkxbeh has quit [Remote host closed the connection]
Pali has joined #maemo-leste
Pali has quit [Ping timeout: 252 seconds]
Pali has joined #maemo-leste
Daanct12 has joined #maemo-leste
Daanct12 has joined #maemo-leste
Daanct12 has quit [Changing host]
Daaanct12 has quit [Ping timeout: 272 seconds]
Pali has quit [Ping timeout: 272 seconds]
Daaanct12 has joined #maemo-leste
Daaanct12 has quit [Changing host]
Daaanct12 has joined #maemo-leste
Buttercat has joined #maemo-leste
<tmlind>
mighty17[m]: if you have your mmc devices moving around, apply commit 77335a040178 ("ARM: dts: Fix moving mmc devices with aliases for omap4 & 5")
<mighty17[m]>
Thanks, so it will start from &mmc1 now?
Pali has joined #maemo-leste
<tmlind>
mighty17[m]: it keeps micro-sd at mmc0 and emmc typically at mmc1
<mighty17[m]>
and sdio would be mmc(x-1) right
<tmlind>
mighty17[m]: depends where it's wired, but keeps the order specified in the aliases
<mighty17[m]>
yeah basically mmc1(sdcard) -> mmc0 , mmc2 -> mmc1 and so on
<tmlind>
yeah
inky has joined #maemo-leste
uvos__ has joined #maemo-leste
uvos__ is now known as uvos
inky has quit [Read error: Connection reset by peer]
<uvos>
mighty17[m]: forget about the random thing, i missinterpreted something
<mighty17[m]>
yes i know the cause was random mmc names
<uvos>
mighty17[m]: like Wizzup saies the modules thing is strange, the image loades those modules via modules-load.d
<uvos>
you dont need them but if you built omap2plus_defconfig and installed it properly they should exist
<uvos>
(but then not probe)
<mighty17[m]>
<uvos "you dont need them but if you bu"> i installed then in the rootfs/sdcard
<mighty17[m]>
oops reply sorry
<uvos>
so maybe you are building the wrong defconfig or you failed to install the kernel modules to /lib/modules/$(uname)
<uvos>
but then again i would expect the system to not boot at all wthout modules
<uvos>
unless you specified some additional stuff to be built in
<mighty17[m]>
no the modules do get loaded
inky has joined #maemo-leste
<uvos>
ok
<uvos>
so is the pvr module loaded?
<mighty17[m]>
they did show that in simplefb, but even if pvr fails, no ui? not even sw rendering
<mighty17[m]>
uvos: is the /var/log/dmesg of any help
<uvos>
if pvr fails no ui
<uvos>
becuase the ui will try to use libgles and segfault
<uvos>
mighty17[m]: best would be some whay to have an interactive shell on device
<uvos>
mighty17[m]: since you have no serial (im very thankfull motorola made this very easy for us :P) you should setup wpa_supplicant to auto connect
<mighty17[m]>
yes there were comr CRITICAL ERRORS or smth
<mighty17[m]>
s/comr/some
<uvos>
and mv /etc/init.d/dsme /etc/init.d/dsme_
<uvos>
then you should be able to boot to shell
<mighty17[m]>
yeah wifi ssh is the only option ig, how would i do that
<inky>
i don't understand, i think i was able to change the d4 from pc by using usb condom. i forgot the wire and the condom somewhere, and was unable to change d4 for a week. now i got it, d4 is exhausted, and it doesn't take charge, i am trying second day.
<inky>
it wasn't taking charge with usb condom immediately, i had to enter safestram android distro, then it would draw this empty battery with the question mark.
<inky>
and then that battery would start to charge. that was the way.
uvos__ is now known as uvos
<uvos>
if the battery is to low android will (rightfully) refuse to charge it
<inky>
to be precise, that battery would show the slow charge process. and it was usually second time i entered the safstrap android. not the first time.
<uvos>
unfortionatly the mainline kernel can cause the battery to underdischarge
<inky>
omg.
<inky>
so i need to get it out and charge separately?
Pali has quit [Ping timeout: 272 seconds]
<uvos>
if android wont charge it and cpcap dosent charge it without booting yes
<inky>
cpcap is what?
Pali has joined #maemo-leste
<uvos>
in a very narrow band around 3v cpcap will charge the battery slowly while the device is off (led will light). with a condom this should also happen.
<uvos>
a condom should not boot the device
<uvos>
since the id pin should not be disconnected...
<inky>
hmmm, condom boots it. well turns it on, and i see the boot menu.
<uvos>
hmm
<uvos>
with just vbus and gnd connected?
<inky>
well i don't know may be my usb condom is wrong, but this device claims to be that.
<inky>
(:
<uvos>
inky: ok so micro usb has 5 pins
<uvos>
vbus d+ d- and id
<uvos>
a condom could have id connected and still be a condom
<uvos>
but this would boot the device (which is undesirable here)
<inky>
ok i see. the condom i have is not condomy enough.
<uvos>
anyhow if you cant charge via android and have no full condom (with id disconnected) you must charge the battery externaly
<uvos>
sorry
<inky>
okay (:
<inky>
i don't understand, what is 'battery calibration'?
<uvos>
Wizzup: please please review the mce patches that prevent users ending up in this situation....
<uvos>
inky: hmm?
<inky>
is it something about internals of the battery or is it something inside the os that knows the battery better.
<uvos>
bettery callibration where?
<uvos>
just that the os knows the battery
<inky>
well, since i changed the battery it is 'uncalibrated'.
<uvos>
inky: yeah sure thats fine
<uvos>
its allways uncalibrated in leste untill the device sees full or empty on that boot btw
<uvos>
this dosent affect anything but the accuracy of the battery display
<inky>
i mean that means leste 'remembers' something about the battery.
<inky>
what is calibration, so can battery be calibrated in leste but uncalibrated in android?
<inky>
just interesting.
<uvos>
inky: yeah sure
<uvos>
but andorid hides the callibrated state anyhow
<inky>
okay.
<uvos>
i dont think it ever tells you if it knows
<inky>
now i think i understand it better.
Buttercat has joined #maemo-leste
Pali has quit [Ping timeout: 272 seconds]
<inky>
uvos, i found a charger that doesn't boot it, and green led lights up. (:
<Wizzup>
uvos: ok. tomorrow I can do all of that, will you be around to coordinate?
<uvos>
Wizzup: do you have some time after 17 CEST till around 21?
<Wizzup>
yeah, I think that should be fine, I might have a mtg around 1830 but otherwise I have time
<uvos>
ok
<Wizzup>
uvos: sorry it's taking a while, I just got the place where I will spend several months so I'm more stable now
<Wizzup>
(and I have the tablets here, and soon lab psu, and pinephone, and d4, and bionic, and d3 ... :-D)
<uvos>
Wizzup: no stress
<uvos>
nice :)
* uvos
is doing 700 ish package upgrade on n900
<Wizzup>
ehe
<Wizzup>
yeah, I need to fix the locale gen and language applet to make it work
<uvos>
that will finish like thusday
<Wizzup>
there's some weird bug
<uvos>
ok
<Wizzup>
for me all the entries get set to "Nederlands" (Dutch) and one to English
<uvos>
btw due to me being an idiot all d4s where playing music in downmixed mono
<uvos>
upps
<uvos>
(on headphones)
<Wizzup>
I saw that yeah, does it affect earpiece in any way?
<uvos>
no
<Wizzup>
ok
<uvos>
oh yes the change dosent affect earpice
<uvos>
but the earpice profile has the same bug
<uvos>
Wizzup: (which is what you ment i assume)
<Wizzup>
well, earpiece is mono though
<uvos>
right
<uvos>
but the earpice profile dosent switch out of mono
<Wizzup>
ah
<uvos>
so if you go internal speaker -> earpice -> headphones