I have connected an external RTC module (ds3231) to a Rock 64/4g.

I've loaded i2c-dev modules and rtc-ds1307 modules but my rtc mod is not detected by i2c (i2cdetect shows nothing connected at address 68)

Hardware is ok (if I boot with ayurfan distro I can see the external RTC module).

Could it be a kernel configuration problem? Has anyone had similar experience?

My Linux distro is Arch Linux Arm.

Regards

Max

I like many others have remained focused on ub ports since the bulk of PP users either seem to use it or postmarket. I love the UI and responsiveness, consistent operating temp and overall stability. We appear to be very close to a working daily driver yet many things seem incomplete, held up in dev for a long time and it is taking a long time to iron out many bugs. Aside from UBports, i thought mobian may be showing the most promise and fastest progress. Until today, i checked into the very quiet Manjaro forum which has had limited activity and voila! Guess what? Looks like they have almost everything working and stable. Im posting this here under UB ports for one reason: i really like ubports and i think its got amazing potential. I think the devs here should take a good hard look at what Manjaro has quickly and simply done with a smooth and rapid roll-out. I feel some lessons can be learned and we can get ubports up to par! Perhaps ub & pmos got a bit too big and complex too fast making it harder to troubleshoot while manjaro kept it simple?

I have an original PBP, with the ISO keyboard. I see that both keyboards are available in the store, for a very reasonable ~ $20. My question is how difficult will it be to swap out the keyboard? Anyone with experience? Thanks.

All of the tutorials and videos I've seen look really super cool but before I go flashing/reformatting the watch and installing something new, I'd like to poke around in out of the box. The documentation states it ships with Infinitime but the documentation page for Infinitime is blank. 
How do I get started and dig around?
Current equipment FYI: I bought a Raspberry Pi and ST-Link and have both a MacBookPro and an ancient Dell with Linux

Most of my knowledge is in web development, dev-ops, and a fair amount in Linux tooling. One thing I've always wanted to learn was working with OS-level programming, but I've never really had a good excuse to get into it until I got a Pinephone. I've taken a university course where I've written programs in C that do system-level calls, as well as creating some simple ARM assembly code, so I suppose I do have a little experience.

To start simple, if I want to for example create a CLI tool that toggles the flashlight on the Pinephone, what fundamentals should I learn first before going about that? I'd also like to try and make a CLI tool to interface with the modem on the Pinephone just for the learning experience.

The material for OS-level programming feels a bit impenetrable for a noob like me, so maybe you guys have some good suggestions?

So I bought a Pinebook Pro and it stopped charging within 3 days. I look on that forum and see this is a common problem, and that you have to open up the laptop, disconnect the battery, plug it in, then plug in the battery to "shock the system" into working again. I also read that it often takes many many times for this to work.  I did this. I did it many dozens of times, multiple days over the course of two weeks. It never worked.

Then I realize the cord itself might be crap, so I switched it to direct power mode and tried plugging it in. Nothing happened, the cord itself failed.  I submitted a complaint to Pine and explained this.

Here's what happened: 

A day and a half after I submit the problem, Pine replied and tells me to check it with a multimeter or the USB-C cord they didn't send with the computer. I tell them I'm unable to do either of those things, this is the only charger they sent. 

Three days later they day they don't understand what my problem is, because my ticket only says "power cord failed". Did they delete the detailed description I typed in? I retype the entire description. 

Three days later, they respond asking me to try opening it up and putting it into direct power mode (i.e., the thing I already did a week before). I am to inform him whether or not the light blinks.  I tell him I already did this a week ago and already told them twice.

Two days later I get a response simply asking of the light blinks or not.  I reply *again* that the light does not blink, as I've stated three times now.  In this time I got a multimeter and checked the power cord. It had failed, no electricity came through it. I sent another email telling Pine this, too.

Two days later Pine tells me I needed to borrow somebody's USB-C cord to try that.  I don't have one to borrow so I had to go buy one and, wouldn't you know it, it charges the laptop because *the power cord was what failed* 

So for those unable to keep track of how long that all took, it failed within 3 days, I spent several weeks trying this "just keep zapping your battery" thing, then got jerked around by Pine on email between July 27th and August 12.  Today Pine told me tough luck because I'm now two weeks out of warranty. 

This is a warning to anybody considering Pine products - you will receive no useful help from anyone at the company, any products you buy will take months to arrive, and it's cheap Chinese product sold as-is.  Just consider it like you bought a used laptop of eBay.

Is anyone else getting really slow eMMC flashing speeds. I just recently flashed it with Belena etcher using the Jumpdrive method and Its been getting speeds around 10mbps and even less. Another thing is that using the Belena etcher which may have been 1.5.101 has resulted in errors. Ive even used gnome disks and the speeds have been slow as well.

And no I did not use  Telenet

I use pinephone Brave Heart edition with mobian as daily phone. It nearly works fine for my use. Thanks a lot for mobian !

I still have an issue to set correctly the volume of the ear piece. When I set it whith alsamixer or phosh settings, the value is sometime changed (during reboot for instance).

In alsamixer, master is at 100%, and earpiece at 100%. It is too much for my earpiece that is sounding very bad, making phone call difficult to hear because volume is too high with a lot of cracks. The range where the sound is ok is very small compared to the setting range in phosh settings. If I change the values in phosh settings and make a test of earpiece and go back to alsamixer, those values are back again to 100%.

I don't know which part of the software is storing the sound settings, I guess, it is not alsamixer. So if you can explain me how it is dealt with, I would be extremely gratefull.

Is there a way to avoid sound setting changes if not manually applied by the user ?

Thanking you in advance for your help !

iv'e recently installed debian on my PBP. in contrary to the Majarno, the speakers and the headphones output did not work at all. iv'e searched the subject online but couldn't find a solution. how do i turn the speakers on? and the headphones output as well? 

So I finally found the time to look into the Clusterboard I got a while back, but strangely enough I can't even get it to turn on

I only have ATX power supply for now (tried two different ones) and the little green light on the Sophine modules turns on when I connected it.

However everything else stays dark.

When I short circuit the two pins in the power switch connector as seen on this pictures:
https://imgur.com/gallery/u9dDsXS
the red power light next to the ATX connector shortly flashes but that's it. Only when I continously connect the two pins of the power switch the lights of the Clusterboard come to life and it seems to cycle through some test program or so, but as soon as the power switch is not short circuted everything goes black again.

I also got a single 15W10ohmJ resistor block and I tried to connect it both to the 3.3V and the 12V holes as seen in the link above, but other than that it gets extremely hot on the 12V, there is no difference in the behaviour of the cluster board.

Did I already accidentially break it with my clueless tinkering?

Edit: for testing I only connected 1 or 2 modules with the emmc and a sd card, so I don't think the problem is what others have described with all 7 modules connected.