| uvos | Wizzup: hi :) | 00:14 |
|---|---|---|
| uvos | mz608 has the less locked bootloader | 00:14 |
| uvos | i would start with that | 00:14 |
| Wizzup | hey | 00:15 |
| Wizzup | ok | 00:15 |
| Wizzup | do you think the kexecboot utags from mz609 will work? | 00:15 |
| uvos | to my knowlage the bootloader dosent care about the device string in utags and the partition layout is the same enough, but you should check the latter in android | 00:16 |
| uvos | since the modem partions might be missing on mz608 | 00:16 |
| Wizzup | I'll boot it to android | 00:16 |
| uvos | on mz608 flashing wrong utags is also no issue since you should be able to just issue a erase via fastboot | 00:16 |
| uvos | (try it first ofc) | 00:17 |
| Wizzup | yeah, I need to check if I have the right android images for it | 00:17 |
| uvos | on mz61* incrorect utags is a hard brick | 00:17 |
| Wizzup | I'm so used to just doing it for the droid 4 that I need to remind myself of all the steps I have to do on the other ones :) | 00:17 |
| uvos | you dont need any android images to undo utags | 00:17 |
| uvos | its just erase | 00:17 |
| uvos | the stock utags is emtpy | 00:17 |
| Wizzup | ok | 00:17 |
| Wizzup | and I guess I should take a droid4 image and make it load the right dtb after kexecboot is set up | 00:18 |
| uvos | yes | 00:18 |
| uvos | wel no | 00:18 |
| uvos | you need to build a new kernel | 00:18 |
| Wizzup | ah, we don't have the dts in the -devel kernel yet? | 00:19 |
| uvos | the kernel we have in devel dosent have the hacks required for the display either | 00:19 |
| Wizzup | I see | 00:19 |
| uvos | https://github.com/maemo-leste/droid4-linux/tree/maemo-6.6 | 00:19 |
| uvos | this one dose tho | 00:19 |
| uvos | but i have never tried it on mz6xx | 00:19 |
| Wizzup | ok, would it make sense to build that for -experimental ? | 00:20 |
| uvos | sure | 00:20 |
| uvos | it works fine | 00:20 |
| uvos | just the cpufreq issue | 00:20 |
| uvos | i have not had the time to look at again | 00:20 |
| Wizzup | ok | 00:20 |
| Wizzup | well, that's better than no display :) | 00:20 |
| Wizzup | looks like I have a flash-mz609-android.sh script, from jan 16 2023, hrm | 00:20 |
| uvos | mz609 android for sure wont work on mz608 | 00:20 |
| uvos | since it will try to flash modem stuff | 00:21 |
| Wizzup | right, I wasn't planning to flash it, I was just browsing to see what I have | 00:21 |
| Wizzup | I do have some mz607 files | 00:21 |
| uvos | flashing single partitions might be ok however | 00:21 |
| Wizzup | $ ls mz607|cat | 00:21 |
| Wizzup | 1.6.0M-272.15_MZ607_p2HW_BlurRegion01_APCFC1FF_fastboot_signed_latam.xml.zip | 00:21 |
| uvos | not sure what the difference between 607 and 608 is even if any | 00:21 |
| Wizzup | Motorola+Xoom+2-RETAIL_MZ607_1.6.0_278_1FF.xml_By(DzTechPhone.Com).zip | 00:21 |
| Wizzup | RETAIL_7.7.1-85_MZ607-31_CFC_1FF.xml.zip | 00:21 |
| Wizzup | RETAIL_MZ607_1.6.0_278_1FF.xml.zip | 00:21 |
| Wizzup | mz607 has no modem, mz608 has modem | 00:22 |
| Wizzup | https://www.gsmarena.com/motorola_xoom_2_media_edition_mz607-4306.php | 00:22 |
| uvos | ah ok | 00:22 |
| Wizzup | https://www.gsmarena.com/motorola_xoom_2_media_edition_3g_mz608-4465.php | 00:22 |
| Wizzup | according to this at least | 00:22 |
| uvos | i thought only 609 had a modem | 00:22 |
| Wizzup | mz608 has a microsd slot, so somehow it has modem and microsd then | 00:23 |
| uvos | yeah seams like the best version then even | 00:23 |
| Wizzup | let me see what kernel this has | 00:24 |
| uvos | well no lte (which acutally might even work in eu on 609) | 00:24 |
| Wizzup | current is android 3.2.2, system version 0.268.4.mz608.retail.en.eu | 00:24 |
| Wizzup | baseband is x1_01.49.00RU | 00:25 |
| Wizzup | linux is 2.6.35.7 | 00:25 |
| uvos | uh ainchent | 00:25 |
| Wizzup | yeah, seems like I might need to find an image to flash to it | 00:25 |
| uvos | thats honycomb the only android version for which soruce was never released | 00:25 |
| Wizzup | heh | 00:26 |
| Wizzup | https://mobilefirmwaredownload.blogspot.com/2014/02/motorola-xoom-2-mz607-mz608-mz616.html | 00:26 |
| uvos | googles explenation for this: the code is to bad (no joke) | 00:26 |
| Wizzup | Blur_Version.77.128.14.MZ608.Retail.en.EU seems like the one to get | 00:26 |
| uvos | yes | 00:26 |
| Wizzup | ia doesn't have it | 00:27 |
| Wizzup | not this again :D | 00:28 |
| uvos | :( | 00:28 |
| uvos | i only grabbed the 609 version | 00:28 |
| Wizzup | https://web.archive.org/web/20130820232527/http://sbfdownload.droid-developers.org/xoom2/7.7.1M-128.14-FLEMEM_SIGN_USAPASTE02RTEUE102A.0R_UCATBLTICSUMRTCOREEU_P010_p2_fastboot.xml.zip | 00:29 |
| Wizzup | from this chinese website: http://sbf.ihei5.com/MZ616/ | 00:29 |
| Wizzup | searched on md5 | 00:30 |
| Wizzup | let's see if it is correct | 00:30 |
| uvos | https://firmware.center/firmware/Motorola/Xyboard%20%28Xoom%202%2C%20Droid%20Xyboard%29/Stock/ | 00:30 |
| uvos | theres also several here, not sure what android version is behind for instance RETAIL_7.7.1-85_MZ607-31_CFC_1FF.xml.zip | 00:30 |
| Wizzup | 77 seems to be 4.0.4 in other filenames | 00:31 |
| uvos | ok but thats 607 anyhow | 00:31 |
| uvos | we should grab all the stuff from firmware.center while its still around | 00:32 |
| uvos | that website went away for like 6 months before allready | 00:32 |
| uvos | who knows how long it will stick around | 00:32 |
| Wizzup | I can store any amount of data, do you have a way to gab it? | 00:32 |
| uvos | no maybe we cant get a hold of the website "Zorge.R" owner for a dump | 00:34 |
| uvos | zorg.rhrd@gmail.com apperantly | 00:34 |
| Wizzup | sounds like it is worth a shot | 00:35 |
| Wizzup | so I guess the procedure is to flash new android, and then perhaps find allow-mbmloader-flashing-mbm.bin (if necessary) | 00:42 |
| Wizzup | then flash kexecboot to the right place | 00:42 |
| Wizzup | same for utags | 00:42 |
| uvos | yes necessary | 00:42 |
| uvos | otherwise yes | 00:42 |
| uvos | same procedure as on d4 | 00:42 |
| uvos | just different partition for kexecboot | 00:42 |
| Wizzup | not bpsw I assume | 00:43 |
| uvos | yes | 00:43 |
| uvos | you dont really have to update android | 00:43 |
| uvos | you could just flash the kernel only | 00:43 |
| uvos | ofc updateing android is good too | 00:43 |
| Wizzup | I want a working android to be able to charge, this is not hooked up to the lab psu yet | 00:43 |
| uvos | right, yeah | 00:43 |
| Wizzup | I am looking at the latam (latin america) zip that I downloaded already | 00:44 |
| uvos | altho presumably on mz60x the battery charging via cpcap only isent quite as bad | 00:44 |
| Wizzup | flash_fastboot.bat | 00:44 |
| Wizzup | it has this: | 00:44 |
| Wizzup | fastboot flash motoboot motoboot.bin | 00:44 |
| Wizzup | fastboot flash boot boot_signed | 00:44 |
| Wizzup | fastboot flash recovery recovery_signed | 00:44 |
| Wizzup | but no mention of mbm specifically | 00:44 |
| Wizzup | I do see ota/mbmloader_ns.bin and ota/mbmloader_hs.bin | 00:44 |
| uvos | not every update updated everything | 00:44 |
| uvos | you may have to grab other updates to get a full set | 00:45 |
| Wizzup | the other zip is similar | 00:45 |
| Wizzup | I have this atm: | 00:45 |
| Wizzup | $ ls *FLEM*|cat | 00:45 |
| Wizzup | 7.7.1-141-7-FLEM-UMTS-LA_MZ608_p2HW_BlurRegion06_CFC1FF_fastboot_signed_latam.xml.zip | 00:45 |
| Wizzup | 7.7.1M-128.14-FLEMEM_SIGN_USAPASTE02RTEUE102A.0R_UCATBLTICSUMRTCOREEU_P010_p2_fastboot.xml.zip | 00:45 |
| uvos | well without a android update.zip with /system or a fastboot image of /system | 00:46 |
| uvos | updateing android will go nowhere | 00:46 |
| Wizzup | I think these zips contain android | 00:46 |
| Wizzup | oh, hm | 00:47 |
| uvos | so there are recovery zips (used by technicians to recover a bricked device) those contain system.img etc | 00:48 |
| uvos | and there are update.zips ment to be executed by android recovery for the purposes of otas | 00:48 |
| Wizzup | well there is | 00:48 |
| Wizzup | 600M -rw-rw-rw- 1 merlijn merlijn 600M Aug 9 2012 system_signed | 00:48 |
| uvos | those contain an android file structure | 00:48 |
| uvos | ok thats a system image | 00:48 |
| uvos | its just named wierd | 00:48 |
| Wizzup | YEAH | 00:48 |
| uvos | so what you have is a recovery zip | 00:48 |
| Wizzup | sorry caps | 00:49 |
| Wizzup | yeah, they're about 1.6GB in data | 00:49 |
| Wizzup | (compressed 500MB or so) | 00:49 |
| Wizzup | anyway maybe it's best if I continue with this tomorrow | 00:50 |
| Wizzup | will you be around in case I inevitably have questions? :P | 00:50 |
| Wizzup | (also, good to know charging on mz607/608/609 might not be as bad) | 00:50 |
| uvos | tomorrow will be sparse | 00:50 |
| uvos | youll manage :P | 00:51 |
| Wizzup | probably not, but I'll get some scripts to flash android at least :P | 00:51 |
| Wizzup | the zip files contain a .bat script so those are easy to convert | 00:51 |
| Wizzup | did we have some allow-mbmloader-flashing-mbm.bin for mz60x ? | 00:52 |
| Wizzup | tony's commit message to kexecboot mostly mentions not having it for mz617 | 00:52 |
| uvos | yes we do | 00:53 |
| Wizzup | oh yeah I see it for mz609 | 00:53 |
| uvos | its not for mz609 its really for 607 | 00:53 |
| uvos | but it dosent matter | 00:53 |
| Wizzup | would I be wrong to assume that would work for mz608? | 00:53 |
| Wizzup | I see | 00:53 |
| uvos | the signing keys are the same | 00:53 |
| uvos | for mz6xx they changed how they updated the bootloader | 00:53 |
| uvos | so they dident need allow-mbmloader-flashing-mbm.bin anymore | 00:53 |
| uvos | for some reason it was still used once on an ota update | 00:54 |
| Wizzup | ok | 00:54 |
| uvos | we have that update for mz607, all other versions are lost to history | 00:54 |
| Wizzup | sorry if I asked these things before, somehow these things don't quite stick to my memory :) | 00:54 |
| uvos | np | 00:54 |
| Wizzup | so where to I flash kexecboot to for mz60x | 00:54 |
| uvos | android cache | 00:54 |
| uvos | it tells you in the utags file name | 00:55 |
| Wizzup | ah | 00:55 |
| Wizzup | this might be the 16GB model | 00:56 |
| Wizzup | well, looks like there is only 16GB | 00:56 |
| Wizzup | for mz607/mz608 | 00:56 |
| Wizzup | ah no, mz607 can have 32GB, but mz60 doe snot | 00:57 |
| uvos | i wonder who comes up with these things | 00:57 |
| Wizzup | yup | 00:57 |
| uvos | some one at motorola: so in the us they get 32gb and lte but dont need a sdcard, in latin america not lte but an sdcard etc | 00:58 |
| uvos | seams really random | 00:58 |
| Wizzup | mz608 also does not have lte it seems | 00:58 |
| uvos | yeah different modem it seams | 00:58 |
| Wizzup | ok, right, so that's why it has microsd | 00:58 |
| Wizzup | since there are no two modems | 00:59 |
| uvos | mz609 has only one modem | 00:59 |
| uvos | its a more modern qcom modem than d4 | 00:59 |
| uvos | that can do lte | 00:59 |
| Wizzup | I see | 00:59 |
| uvos | there is no lcm2.0 in mz6xx | 00:59 |
| uvos | no idea about what is in 608 then, but something else presumably | 00:59 |
| uvos | probubly mbm6600 going by specs | 01:00 |
| Wizzup | will probably know more tomorrow | 01:05 |
| Wizzup | is it a lot of work to kick off a kernel from experimental for the branch you linked earlier? | 01:05 |
| Wizzup | btw, the utags for mz609 are for 32GB I think, so this might be a problem | 01:06 |
| Wizzup | also, tdlib on armhf runs out of address space in cc1plus :( | 01:08 |
| Wizzup | ok, worked around that with -O1 for now | 02:00 |
| tmlind | Wizzup: i only tested flashing mz608 as mz609 after clearing that one partition, did not try doing it on mz615 so far | 04:58 |
| tmlind | uvos: possibly if you mess up utags on mz617 and then reset the device from recovery utags also gets reset, unconfirmed though | 05:00 |
| tmlind | hmm so which xyboard tablet models have a working micro-sd then? | 05:01 |
| tmlind | the mz609 variants have a sucky touchscreen controller not supported in the mainline kernel btw, vendor upstreamed earlier controller then never bothered to send updates so nobody has cared about the new controller i think | 05:03 |
| tmlind | i'll be sending the updated display bridge patches to the lists after -rc1 | 05:04 |
| tmlind | with those mz617 should be mostly usable with mainline kernels | 05:04 |
| freemangordon | Wizzup: ping | 10:07 |
| freemangordon | I need some help with gdbus | 10:07 |
| Wizzup | freemangordon: hi | 10:39 |
| freemangordon | hi | 10:39 |
| Wizzup | tmlind: mz608 should have working microsd, as does mz607 I think | 10:39 |
| freemangordon | Wizzup: how should I iterate over "(@a(oa{sv}))" ? | 10:39 |
| freemangordon | 'o' is object path I guess | 10:40 |
| freemangordon | but what is a{sv}? | 10:40 |
| freemangordon | array of? | 10:40 |
| freemangordon | what? | 10:40 |
| Wizzup | I think thas is a map | 10:41 |
| Wizzup | hang on | 10:41 |
| freemangordon | ah, dictionary | 10:41 |
| freemangordon | right | 10:41 |
| Wizzup | a{sv} is a map[string]=variant | 10:42 |
| Wizzup | I think | 10:42 |
| freemangordon | hmm, ok | 10:43 |
| Wizzup | do you have some example of this in dbus, or not? | 10:43 |
| freemangordon | no idea | 10:44 |
| Wizzup | I am looking at my wpaicd.c code from libicd-network-wpasupplicant to see if there is anything analogous | 10:44 |
| Wizzup | is this tp related? | 10:44 |
| freemangordon | I think it should be while (g_variant_iter_loop (iter, "(oa{sv})", &path, &map) ) | 10:44 |
| freemangordon | ofono | 10:44 |
| freemangordon | GetModems | 10:44 |
| Wizzup | I see | 10:44 |
| Wizzup | and yes o is object path, so (oa{sv}) is a tpuple of two values, with the first being an object path and the second a map | 10:45 |
| Wizzup | so I think this is indeed ok | 10:45 |
| freemangordon | ok, thanks | 10:45 |
| Wizzup | btw, I don't know how tricky this would be, and maybe it already does, but if tp-haze could export some of the Room interfaces, it could be used to get channel identifiers | 10:50 |
| Wizzup | like on telegram the channel ids are just chat-124435435343 | 10:51 |
| freemangordon | Yes, I know | 10:51 |
| Wizzup | ah ok :) | 10:51 |
| freemangordon | actually, I ythink we already do it, at least partially | 10:51 |
| freemangordon | but I didn't dig much into it | 10:51 |
| Wizzup | ok, it might also depend on the purple plugin being loaded | 10:52 |
| Wizzup | I could definitely get the participant names btw :) | 10:52 |
| Wizzup | just not the room title | 10:52 |
| freemangordon | see https://github.com/maemo-leste-upstream-forks/telepathy-haze/commit/b06ed7a2e579a8998e0ed8e1504fdb66c47ce3c3 | 10:52 |
| freemangordon | I had no idea what to do there | 10:52 |
| freemangordon | feel free to fix it | 10:52 |
| freemangordon | I can't test with FB as there is no room name there | 10:53 |
| freemangordon | just an id | 10:53 |
| Wizzup | I meant like this: https://web.archive.org/web/20231116152346/https://telepathy.freedesktop.org/spec/Channel_Interface_Room_Config.html | 10:54 |
| Wizzup | right @ fb | 10:54 |
| freemangordon | that one as well | 10:54 |
| Wizzup | it looks like telegram and discord have the same | 10:54 |
| Wizzup | I think the id is probably correct as it is now in haze | 10:55 |
| freemangordon | perhaps UI can do something smart, like combining nicks | 10:55 |
| freemangordon | or avatars, dunno | 10:55 |
| Wizzup | hm? | 10:55 |
| freemangordon | to create some meningful room name | 10:56 |
| freemangordon | *meaningful | 10:56 |
| Wizzup | I think if we implement the room config in haze we'll get it for free | 10:56 |
| freemangordon | could b | 10:56 |
| freemangordon | e | 10:56 |
| Wizzup | or rather, we'll get the right behaviour | 10:56 |
| freemangordon | but where we will get the name from? | 10:56 |
| Wizzup | purple | 10:56 |
| freemangordon | it does not provide | 10:56 |
| Wizzup | I think it does | 10:56 |
| freemangordon | at least for FB | 10:56 |
| Wizzup | mhm | 10:56 |
| freemangordon | in pidgin I see the same big int | 10:57 |
| Wizzup | btw, I ended up building tdlib (the telegram purple lib) with -O1 | 10:57 |
| freemangordon | that's why I said I cannot test | 10:57 |
| Wizzup | armhf ran out of memory with -O2 | 10:57 |
| freemangordon | yeah, I saw it | 10:57 |
| Wizzup | like, because it's 32 bit | 10:57 |
| freemangordon | heh | 10:57 |
| freemangordon | what TF do they do? | 10:57 |
| Wizzup | don't know, could also be a poor path in gcc somehow | 10:57 |
| Wizzup | the memory usage is pretty good though | 10:58 |
| Wizzup | freemangordon: btw, what should trigger icon update cache? | 11:06 |
| Wizzup | now if I install a rtcom-accounts-plugin-... I don't get the icons until I manually update the cache | 11:08 |
| Wizzup | also, looks like apparmor isn't running on d4 hehe | 11:08 |
| freemangordon | I think you should call from postinst, lemme check | 11:09 |
| Wizzup | ok | 11:09 |
| Wizzup | that's easy in that case | 11:09 |
| freemangordon | https://github.com/maemo-leste/rtcom-accounts-plugins/blob/master/debian/rtcom-accounts-plugins.postinst | 11:09 |
| Wizzup | ok thanks | 11:13 |
| freemangordon | Wizzup: how to get value from dictionary? shall I iterate? | 11:16 |
| freemangordon | ah g_variant_lookup_value | 11:17 |
| Wizzup | yeah | 11:19 |
| Wizzup | sicelo: hm, having trouble with totp and gitlab now | 11:19 |
| Wizzup | digging deeper in this tablet with mz608 firmware, I don't see a microsd card, only a sim slot, so that's a bit weird | 11:45 |
| Wizzup | this mz616 definitely has one though | 11:47 |
| Wizzup | I suppose for mz616 the dts will need to be modified to support a microsd | 11:50 |
| Wizzup | actually looks like common still has mmc1 entry | 11:51 |
| Wizzup | ah, ok, yeah, the tablet dts overrides it | 11:56 |
| Wizzup | tmlind: anything meaningful I can extract from mz616 with android 4.0.4? maybe where microsd card and where modem is? | 12:01 |
| Wizzup | I've at least verified that this mz616 has both microsd and modem working in android 4.0.4 | 12:02 |
| sicelo | Wizzup: what's the problem? | 12:03 |
| * sicelo is not available though, at least for next 6 hours | 12:04 | |
| Wizzup | sicelo: 'did not work' :) | 12:06 |
| Wizzup | maybe I need to sync time or sometghing | 12:07 |
| Wizzup | sicelo: as in, code not accepted | 12:07 |
| Wizzup | it's not too important, I'll debug that later | 12:07 |
| sicelo | ok. plausible @time | 12:07 |
| sicelo | otherwise on the d4, i have a token for gitlab | 12:09 |
| Wizzup | ok | 12:23 |
| tmlind | Wizzup: ok, not sure if the microsd is added properly on any tablets as it's not working on mz617 | 12:37 |
| tmlind | the mmc regulator is different from d4 i recall | 12:37 |
| Wizzup | mz616 has a working microsd | 12:38 |
| Wizzup | I tested it on android 4.0.4 just now | 12:38 |
| Wizzup | inserted a microsd card and formatted it through the android ui | 12:38 |
| tmlind | ok, if you get a chance to open one at some point would be interesting to see if there are some extra components populated on the micro-sd card cable compared to mz617 that seems to be missing the micro-sd cage | 12:44 |
| tmlind | tried popping in a micro-sd card to mz608, it seems to move sideways in the slot, not sure if it's functional | 12:47 |
| Wizzup | I'll open up the mz616 today | 12:49 |
| Wizzup | wrt mz608, is that the sim slot or microsd card slot | 12:50 |
| Wizzup | I thought it was a microsd card slot on my mz608, but I think it is the sim slot | 12:50 |
| tmlind | yeah might be hard to see | 12:52 |
| tmlind | here's a picture of the unpopulated mz617 sim + micro-sd cable: https://www.ebay.com/itm/223086871933 | 12:52 |
| Wizzup | if you peek inside it you might see that it has 3 pins close to the entry | 12:52 |
| Wizzup | I think that is why they are sim, not microsd | 12:52 |
| Wizzup | microsd needs a whole array of pins deep inside the port | 12:52 |
| tmlind | yup that would explain why the card moves sideways :) | 12:53 |
| tmlind | need to go out here, bbl | 12:53 |
| Wizzup | ha, this cable you linked can be used to add a microsd to mz617? | 12:54 |
| Wizzup | ok ttyl | 12:54 |
| Wizzup | oh, sim card. | 12:54 |
| Wizzup | tmlind: do you know if the digitiser should work with the case removed? or does it detect this somehow? | 16:44 |
| Wizzup | hah, nevermind, the cable was loose | 16:46 |
| Wizzup | let me make those photos | 16:47 |
| sicelo | so i copied the totp key from my android phone (aegis from f-droid), entered it in maeotp. the generated codes are the same | 16:50 |
| Wizzup | sicelo: ok, must have been time related then\ | 16:54 |
| Wizzup | tmlind: https://wizzup.org/dirlist/mz616/ | 17:05 |
| Wizzup | do you need me to also open up a mz617? | 17:07 |
| Wizzup | sicelo: yeah, time was 59s off | 18:58 |
| sicelo | ah :-) | 19:16 |
| arno11 | hi guys, i noticed few things today: idle current draw increased a bit on N900: around 8-10mA (modem On, screen Off, hspda network: 57mA instead of 47). there is no effect if i change cpu frequency: same result @250MHz and 850. BTW default governor 'ondemand' doesn't work properly and keeps the max freq available all the time | 19:44 |
| Wizzup | if it is with internet on, it could just mean the modem is idle less often? | 19:46 |
| arno11 | conservative governor works far better | 19:46 |
| arno11 | internet is off | 19:46 |
| Wizzup | oh, I got confused because you said HSDPA network | 19:46 |
| Wizzup | you meant just 3.5g? | 19:46 |
| arno11 | ah ok | 19:46 |
| arno11 | yes | 19:46 |
| Wizzup | did anything change on your side? | 19:47 |
| arno11 | absolutely nothing | 19:48 |
| arno11 | idle was usually around 47 since march 2023 in normal conditions | 19:49 |
| Wizzup | when was the draw 47mA? | 19:49 |
| arno11 | wdym exactly ? | 19:50 |
| Wizzup | you wrote it was 47mA | 19:51 |
| Wizzup | when did you measure this? | 19:51 |
| arno11 | every weeks usually | 19:52 |
| arno11 | idle current draw has been stable and the same for several months | 19:53 |
| Wizzup | is iphbd installed? | 19:55 |
| arno11 | iirc yes | 19:55 |
| Wizzup | can you check? | 19:56 |
| arno11 | yes it is installed | 19:57 |
| Wizzup | hm | 20:00 |
| arno11 | stopping it and things are back to normal :) | 20:01 |
| freemangordon | hmm, that's weird | 20:02 |
| freemangordon | it should decrease the usage, not increase :) | 20:03 |
| arno11 | lol indeed that's a problem | 20:03 |
| freemangordon | do you have iphb module loaded? | 20:03 |
| arno11 | ah it seems to not be loaded by default | 20:04 |
| freemangordon | it is loaded, if it is build at | 20:04 |
| Wizzup | tmlind: apart from no microsd holder from my photos there does not seem to be a difference between mz616 and mz617 | 20:04 |
| freemangordon | arno11: do you have iphb-dkms installed? | 20:04 |
| arno11 | let me check | 20:05 |
| freemangordon | arno11: hmm, stopping iphbd removes the module as well | 20:06 |
| arno11 | ah ok | 20:06 |
| arno11 | (iphb-dkms is installed btw) | 20:06 |
| freemangordon | still, does modprobe iphb loads it? | 20:06 |
| arno11 | nope | 20:07 |
| freemangordon | do you have that module build? | 20:07 |
| Wizzup | find /lib/modules/ | grep iphb | 20:08 |
| Wizzup | (nothing) | 20:08 |
| Wizzup | on d4 | 20:08 |
| freemangordon | why is that? | 20:08 |
| Wizzup | good question | 20:08 |
| freemangordon | /lib/modules/6.1.67/updates/dkms/iphb.ko | 20:08 |
| Wizzup | I don't have that on d4 | 20:09 |
| freemangordon | :( | 20:09 |
| arno11 | i have it on n900 | 20:09 |
| freemangordon | but you can;t modprobe it? | 20:09 |
| Wizzup | dpkg-reconfigure iphb-dkms | 20:09 |
| Wizzup | seems to build it | 20:09 |
| arno11 | indeed i can't load it | 20:09 |
| freemangordon | what is the error? | 20:10 |
| Wizzup | it probes fine for me on d4 | 20:10 |
| arno11 | modprobe : error: could not insert iphb: no such device | 20:10 |
| freemangordon | whaaat? | 20:10 |
| freemangordon | are you sure your FS is ok? | 20:11 |
| arno11 | that's still a fresh install and everything seems ok | 20:11 |
| freemangordon | and you are on 6.1.67? | 20:12 |
| arno11 | yes | 20:12 |
| freemangordon | no idea, I have never seen such an error on modprobe | 20:12 |
| freemangordon | try dpkg-reconfigure iphb-dkms | 20:12 |
| arno11 | ok man | 20:13 |
| arno11 | seems to build | 20:14 |
| freemangordon | arno11: BTW, what is iphb-dkms version? | 20:14 |
| arno11 | 1.5+m7 | 20:15 |
| freemangordon | ok | 20:15 |
| arno11 | build seems ok | 20:15 |
| freemangordon | so, can you modprobe it now? | 20:15 |
| arno11 | let's try | 20:15 |
| arno11 | still doesn't work | 20:16 |
| freemangordon | dmesg? | 20:16 |
| arno11 | with same error | 20:16 |
| arno11 | let me check | 20:16 |
| arno11 | nothing in dmesg | 20:17 |
| freemangordon | could you check with lsmod | grep iphb that it is not loaded? | 20:18 |
| freemangordon | if not, please reboot the device | 20:18 |
| arno11 | rebooting... | 20:18 |
| freemangordon | ok | 20:19 |
| arno11 | loading hildon... | 20:23 |
| arno11 | now i see it with lsmod | 20:24 |
| freemangordon | ok | 20:24 |
| freemangordon | how is idle usage? | 20:25 |
| arno11 | let me check | 20:25 |
| arno11 | 57mA | 20:26 |
| freemangordon | :( | 20:27 |
| freemangordon | use dsmetool to stop iphbd | 20:27 |
| arno11 | ok let's try | 20:27 |
| freemangordon | dsmetool -k /usr/bin/iphbd | 20:27 |
| freemangordon | hmm, wait | 20:28 |
| freemangordon | it is not dsmetool started it seems | 20:28 |
| arno11 | yes indeed | 20:28 |
| arno11 | init.d | 20:29 |
| freemangordon | no | 20:29 |
| freemangordon | do not stop it through init.d script | 20:29 |
| arno11 | ok | 20:29 |
| arno11 | so how we can stop it properly ? | 20:32 |
| freemangordon | trying to find a way | 20:32 |
| freemangordon | sec | 20:32 |
| arno11 | ok | 20:32 |
| freemangordon | arno11: /usr/sbin/dsmetool -U root -k '/usr/bin/iphbd ' | 20:33 |
| arno11 | ok | 20:35 |
| arno11 | Process not killed: not found, not root or kill failed | 20:37 |
| freemangordon | you should do that as root | 20:37 |
| arno11 | yes even as root | 20:37 |
| freemangordon | and just copy/paste /usr/sbin/dsmetool -U root -k '/usr/bin/iphbd ' | 20:38 |
| freemangordon | see the space before the closing apostrophe | 20:38 |
| arno11 | yes i see | 20:38 |
| arno11 | same result | 20:38 |
| freemangordon | ps -ef | grep iphbd | 20:38 |
| arno11 | that's ok now | 20:39 |
| arno11 | iphbd killed | 20:39 |
| freemangordon | sorry, can;t parse | 20:39 |
| arno11 | let's check current draw | 20:39 |
| freemangordon | did you miss that space? | 20:39 |
| arno11 | nope i missed 'd' in iphbd lol | 20:39 |
| freemangordon | why don;t you copy-paste? | 20:40 |
| arno11 | because i'm cooking, using irssi on my wife's pc and working directly in the n900... | 20:41 |
| arno11 | and drinking a tripel karmelitt | 20:41 |
| freemangordon | well, but that's kinda slow and error prone | 20:41 |
| freemangordon | heh | 20:41 |
| freemangordon | maybe I deserve a drink too | 20:41 |
| * freemangordon checks | 20:41 | |
| arno11 | :) | 20:42 |
| arno11 | (the current draw is back to normal again, once iphbd is killed) | 20:42 |
| freemangordon | ok, could you start it as root: | 20:43 |
| freemangordon | /usr/bin/iphbd -d | 20:43 |
| arno11 | ok | 20:44 |
| freemangordon | but please, do that from remote shell, I would need the output | 20:44 |
| arno11 | ok sec | 20:44 |
| Wizzup | uvos: tmlind: ok, have this mz617 on my lab psu now, next is to try leste :) | 20:45 |
| Wizzup | arno11: tripel karmeliet is great :D | 20:45 |
| arno11 | oh yeah :) | 20:45 |
| arno11 | freemangordon: opened client socket 5 to /dev/shm/iphb | 20:47 |
| arno11 | waiting events... | 20:47 |
| arno11 | waiting with sleeptime 3600, nfds=1, clients=0 | 20:47 |
| freemangordon | so, that should not increase idle current :) | 20:47 |
| freemangordon | could you go offline->online with IM accounts | 20:47 |
| arno11 | i doublechecked and there is still 10mA diff | 20:47 |
| arno11 | im accounts are off | 20:48 |
| freemangordon | that does not make sense | 20:48 |
| freemangordon | ok | 20:48 |
| freemangordon | do you have any activity in top? | 20:48 |
| freemangordon | arno11: how do you check idle current? | 20:48 |
| arno11 | nothing unusual | 20:49 |
| arno11 | sleep 30 && cat /sys/class/power blabla/current_now | 20:49 |
| freemangordon | no | 20:49 |
| arno11 | ? | 20:50 |
| freemangordon | you should use current_avg | 20:50 |
| freemangordon | or even better power_avg | 20:50 |
| arno11 | yes but honestly it makes no diff | 20:50 |
| sicelo | there's no current_now on N900, iirc | 20:51 |
| sicelo | i mean, current_avg | 20:51 |
| arno11 | indeed | 20:51 |
| freemangordon | yeah, power_avg | 20:51 |
| arno11 | only power avg | 20:51 |
| freemangordon | if there is such thing | 20:51 |
| arno11 | right | 20:51 |
| freemangordon | ok, use power_avg | 20:52 |
| freemangordon | in the meanwhile I am testing on d4 | 20:52 |
| freemangordon | with/without iphbd | 20:53 |
| arno11 | ok but power_avg is not relevant for idle only imo | 20:53 |
| freemangordon | it is | 20:53 |
| freemangordon | most of the time | 20:53 |
| freemangordon | hmm, it seems the same happens on d4 | 20:53 |
| freemangordon | lets wait 2 more minutes to be sure | 20:54 |
| arno11 | ok | 20:54 |
| Wizzup | uvos: tmlind: well, android also idles in off mode it seems at least | 20:57 |
| freemangordon | arno11: I see no increase here because of iphbd | 20:59 |
| freemangordon | there is something else going on | 20:59 |
| arno11 | freemangordon: results are pretty similar for me (power_avg / voltage_now) | 20:59 |
| freemangordon | voltage_now? | 20:59 |
| arno11 | i mean pretty similar to current_now | 20:59 |
| freemangordon | how is voltage_now relevant? | 20:59 |
| freemangordon | ah | 20:59 |
| freemangordon | ok | 21:00 |
| arno11 | :) | 21:00 |
| freemangordon | so, may I have the output of iphbd? | 21:00 |
| arno11 | i already sent, no ? | 21:00 |
| freemangordon | "waiting with sleeptime 3600, nfds=1, clients=0" is the last? | 21:00 |
| arno11 | yes | 21:01 |
| freemangordon | I don;t see how it could increase idle draw | 21:01 |
| freemangordon | arno11: lets try another thing | 21:02 |
| arno11 | i don't know :( maybe iphb is not directly the root cause ? | 21:02 |
| freemangordon | stop iphbd | 21:02 |
| freemangordon | and start it again as '/usr/bin/iphbd -d -k' | 21:03 |
| freemangordon | you should see 'iphb:TCP keepalive queuing disabled' | 21:03 |
| freemangordon | -k prevents opening kernel module | 21:03 |
| arno11 | ok | 21:04 |
| freemangordon | so we can check if there is any issue there | 21:04 |
| arno11 | yes i got the same msg | 21:05 |
| freemangordon | ok | 21:06 |
| freemangordon | how's the current now? | 21:06 |
| arno11 | currently waiting for the result | 21:06 |
| freemangordon | ok | 21:06 |
| arno11 | argh wifi was on (ssh), need to test again | 21:08 |
| freemangordon | ok | 21:08 |
| arno11 | ah it's better (?!) | 21:09 |
| arno11 | let me check gain | 21:09 |
| arno11 | *again | 21:09 |
| arno11 | got 50mA now | 21:11 |
| freemangordon | ok, but iphbd waits in select(), so it cannot increase the idle draw, iiuc | 21:12 |
| freemangordon | also, the kernel driver is not involved | 21:12 |
| freemangordon | arno11: basically, kernel driver queues keepalives untile there is some other activity | 21:15 |
| freemangordon | so I can;t see how would it increase the idle consumption as it prevents radios from being turned on | 21:15 |
| arno11 | but that's a fact that current draw is higher if we don't restart ipbh properly | 21:16 |
| freemangordon | wthym "properly"? | 21:17 |
| arno11 | like h-s-m or nokia-modem sometimes btw | 21:17 |
| arno11 | i mean using the right command | 21:17 |
| freemangordon | arno11: process waiting in poll() is idle | 21:18 |
| freemangordon | and this is where iphbd stays most of the time | 21:18 |
| freemangordon | if not all the time | 21:18 |
| arno11 | ok | 21:18 |
| freemangordon | so it is something else, IIUC | 21:18 |
| arno11 | maybe something is unstable on boot | 21:18 |
| freemangordon | ? | 21:19 |
| arno11 | i mean, ATM, i have to restart h-s-m, ipbh and sometimes nokia modem after boot | 21:20 |
| freemangordon | why? | 21:20 |
| freemangordon | do you still have issue with presence-ui? | 21:21 |
| arno11 | ofc | 21:21 |
| freemangordon | ok, lets debug that first | 21:21 |
| freemangordon | maybe there is a common root for all the issues you have | 21:21 |
| arno11 | yes i think so | 21:22 |
| freemangordon | so, after boot there is no "availability" button in h-s-m? | 21:22 |
| arno11 | yes | 21:22 |
| freemangordon | and there is no coredomp for h-s-m? | 21:22 |
| freemangordon | *coredump | 21:23 |
| arno11 | no coredumps, i need to go (kids), back in 30 min | 21:23 |
| freemangordon | ok | 21:23 |
| Wizzup | tmlind: for kexecboot on mz617 we need android 4.0.4 as well yeah, not 4.1.2? | 22:11 |
| Wizzup | hm it's still 3.0.8 | 22:12 |
| Wizzup | tmlind: uvos: as I understand it, cache is only 900MB, so that's all we get for our rootfs? | 22:33 |
| Wizzup | ah I see uvos write this (way) earlier: | 22:42 |
| Wizzup | 00:10 < uvos> we have to create a small 600 mb ish image that we flash to preinstall that copyies itself over to userdata and then downloads the rest of the packages | 22:42 |
| Wizzup | ok, so I have root now om mz617, and almost done reading the whole backlog over the last years regarding mz617 | 22:53 |
| Wizzup | it seems like I can nuke some android partitions for mainline now that I have it hooked up to lab psu, since I won't run into battery charging problems | 22:54 |
| Wizzup | one thing that is not clear to me yet is is the utags-mz617-32 are also ok for a mz617 16GB tablet | 22:57 |
| Wizzup | my mz616 is also rooted, and it is 32GB, so it seems like I should be able to get kexecboot on there | 23:06 |
| Wizzup | uvos: tmlind: ok, so I got my mz616 flashed with kexecboot. I dd'd both utags and kexecboot from android, and then I got kexecboot. that booted into android, and that molested my cache partition and thus kexecboot, but then with fastboot I can restore kexecboot and so get back in | 23:34 |
| Wizzup | I think the next step is for me to get some serial set up because kexecboot really quickly just wants to boot to android | 23:35 |
| Wizzup | uvos: you didn't pull in the commits for builddeb in the maemo-6.6 branch | 23:55 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!