PINE64 - User contributions [en]

PinePhone APN Settings

2023-04-29T20:01:55Z

PineMarten: Add APN for Bell Mobility

The [https://en.wikipedia.org/wiki/Access_Point_Name APN] setting is the gateway between your carrier's cellular network and the '''public Internet'''. The APN setting - if not set automatically by the user's OS - has to be set by the user to enable the use of the mobile Internet on the phone.

== Setting the APN ==

The location of the APN setting depend on the user interface the distribution is using.

=== Gnome ===

One of the biggest actively maintained open (Creative Commons Public Domain) database of mobile broadband service providers and their APN settings is maintained by the Gnome project, and is available in their [https://gitlab.gnome.org/GNOME/mobile-broadband-provider-info/-/blob/main/serviceproviders.xml serviceproviders.xml]. It is a rare case, when you don't find your own provider in that list, but if it happens, then please consider contributing to it upstream. If your provider is in that database, then for setting up the APN, you only have to select your provider from the list under <code> Settings > Network > Network Dropdown > Add new connection</code>.

Further details are [https://help.gnome.org/users/gnome-help/stable/net-mobile.html.en described by the Gnome help].

=== Phosh ===

APN settings are either located in <code>Settings > Mobile > Access Point Names</code> (Arch Linux ARM, PureOS, Debian + Phosh) or <code> Settings > Network > Network Dropdown > Add new connection</code> (postmarketOS, Fedora).

=== Plasma Mobile ===

TBD

== List of tested carriers ==

Disclaimer: Go to the websites of or speak to the customer support lines of those carriers which you want to use. No guarantees. This list is simply user-generated and serves to demonstrate examples of what worked for them. This list is not exhaustive, does not cover all possible carriers.

=== 4ka (Slovakia) ===
Name: 4ka Internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.4ka.sk/vitajte/navody-a-nastavenia/detail-navodu

=== AT&T-based ===

==== AT&T (USA) ====
APN: NXTGENPHONE
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net

APN: <code>phone</code> may alternatively work.

Source: https://www.att.com/support/article/wireless/KM1218306/

==== AT&T Mexico (Mexico) ====

APN: <code> wap.attmex.mx </code>

==== Cricket (USA) ====
APN: <code>phone</code> or <code>ndo</code> or <code>NXTGENPHONE</code>

=== Bell Mobility (Canada) ===
APN: <code>apn.bell.ca</code>
MMSC: <code>http://mms.bell.ca/mms.wapenc</code>

=== Blau.de (Germany) ===
APN: internet.eplus.de
Username: eplus
Password: gprs

Source: https://www.my-gps.org/412-apn-einstellungen-deutschland

=== Bouygues Telecom (France) ===
Name: Bouygues Telecom
APN: mmsbouygtel.com
Username: <empty>
Password: <empty>

Source: https://www.assistance.bouyguestelecom.fr/s/article/parametrage-mobile-email-mms-internet

=== Congstar - Telekom Net (Germany) ===
Name: Telekom Internet
APN: internet.telekom
Username: telekom
Password: telekom

Other settings seem to work, too. [https://forum.congstar.de/Tarife/Tarif-Produktberatung/46325-Mobil-surfen-mit-congstar-manuelle-Einstellungen-zum-mobilen-Internet-APN/ Congstar mentions]

Name: Congstar Internet
APN: internet.telekom
Username: congstar
Password: cs

=== Eastlink Wireless (Canada) ===

Name: Eastlink Internet
APN: wisp.mobi.eastlink.ca
Username: <empty>
Password: <empty>

Source: https://www.apnsettings.org/canada/eastlink-ca/

=== Free (France) ===

Name: Free
APN: free
Username: free
Password: <empty>

Source: https://mobile.free.fr/assistance/46.html

=== Freedom Mobile (Canada) ===

Name: 1
APN: internet.freedommobile.ca
Username: <empty>
Password: <empty>

=== Google Fi (USA) ===

These are settings that Google provides for their "data-only" SIM cards, but also appears to work fine with the normal SIM card for texting and calling.

Name: Google Fi
APN: h2g2
Username: <empty>
Password: <empty>

Source: https://support.google.com/fi/answer/6330195?hl=en

=== Hofer Telekom (Austria) ===

Name: HoT Internet
APN: webaut
Username: <empty>
Password: <empty>

Source: https://www.hot.at/config/faqs/HoT_Einstellungen_Endgera_te.pdf

=== kölbi (Costa Rica) ===
Name: Costa Rica:Kolbi:Internet
APN: kolbi3g
Username: <empty>
Password: <empty>

Note: alternatively <code>kolbi4g</code> also works as APN.

=== Koodo (Canada) ===

Name: Internet/MMS 2
APN: sp.koodo.com
Username: <empty>
Password: <empty>

Source: https://www.4gapn.com/ca/en/koodo

=== KT (South Korea) ===

Name: KT LTE
APN: lte.ktfwing.com
Username: <empty>
Password: <empty>

Name: KT 3G
APN: alwayson.ktfwing.com
Username: <empty>
Password: <empty>

Note: APN automatically detected in Manjaro Phosh. Use either KT LTE or KT 3G according to your subscription.

=== Lebara (UK) ===
Name: Lebara
APN: uk.lebara.mobi
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

=== Magenta LTE (Austria) ===

Name: Magenta
APN: internet.t-mobile.at
Username: t-mobile
Password: tm

Source: https://www.magenta.at/faq/entry/%7Etechnische-anfrage%7Esmartphone%7Efunktionen%26dienste/%7EInternet_APN%7Emaster

=== Mineo (Japan) ===

Tested with S plan (Softbank) and D plan (Docomo). Mobile LTE data currently working only on Phosh-based operating systems, because they use Network Manager and Modem Manager. Ubuntu Touch not working yet, see issue #58. https://gitlab.com/ubports/community-ports/pinephone/-/issues/58

Name: Mineo
APN: mineo-d.jp
Username: mineo@k-opti.com
Password: mineo

Source: https://support.mineo.jp/manual/network_setup_d.html

=== Mint Mobile (USA) ===

Call their customer service to activate using the number on their website, or activate on their [https://my.mintmobile.com/activation website]. You may also need to reboot your phone.

Use the following APN settings:

Name: Ultra
APN: Wholesale

Source: https://www.mintmobile.com/setup-for-android/

=== Mobile Vikings (Belgium) ===

Name: Mobile Vikings
APN: web.be
Username: web
Password: web

Source: https://support.vikingco.com/hc/en-us/articles/202836041-I-don-t-have-any-mobile-internet-What-do-I-do-

If the first one doesn't work try this one:

Name: Mobile Vikings
APN: web.be
Username: <empty>
Password: <empty>

Source: autoconfig on ubports

=== Movistar (Colombia) ===

Name: Movistar Internet
APN: internet.movistar.com.co
Username: movistar
Password: movistar

=== Orange Telecom (France) ===
Name: Orange Internet
APN: orange
Username: orange
Password: orange

Source: https://assistance.orange.fr/mobile-tablette/tous-les-mobiles-et-tablettes/depanner/probleme-avec-un-service-d-orange-internet-sms-mms-mails-cloud-tv/mms/configurer-un-apn-internet-et-mms_192948-738196

=== Orange (Poland) ===
Name: Internet IPv4
APN: internet
Username: internet
Password: internet

Source: https://www.orange.pl/omnibook/konfiguracja-internetu-mms-sms-w-telefonie#

Note: don't forget to activate sim-card using official android/ios app.

=== Patriot Mobile (USA T-Mobile) ===
Internet

Name: T-Mobile
APN: Fast.t-mobile.com
Username: <empty>
Password: <empty>

MMS (requires chatty v0.6.1 and mmsd-tng v1.8)

in /home/alarm/.mms/modemmanager/mms

[Modem Manager]
CarrierMMSC=http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS_APN=Fast.t-mobile.com
CarrierMMSProxy=NULL
DefaultModemNumber=NULL
AutoProcessOnConnection=true
AutoProcessSMSWAP=true

[Settings]
UseDeliveryReports=false
TotalMaxAttachmentSize=600000
MaxAttachments=25
AutoCreateSMIL=true
ForceCAres=false

Source: https://www.t-mobile.com/support/devices/not-sold-by-t-mobile/byod-t-mobile-data-and-apn-settings

=== Penny Mobil (Germany) ===

APN settings:

name: Penny Mobil
APN: internet.t-mobile
username: t-mobile
password: tm

=== Public Mobile (Canada) ===
Internet only, mms not tested.

Name: Public Mobile
APN: sp.mb.com
Username: <empty>
Password: <empty>

Source: https://productioncommunity.publicmobile.ca/t5/Phones-Hardware/How-do-I-set-up-data-APN-on-my-smartphone/td-p/3

=== Red Pocket (USA) ===

You can choose AT&T, Verizon, T-Mobile or Sprint network.

APN settings:

name: Red Pocket
APN: RESELLER

=== Rogers (Canada) ===

Name: 4G/LTE Rogers Data
APN: ltemobile.apn
Username: <empty>
Password: <empty>

Name: 3G Rogers Data
APN: internet.com
Username: wapuser1
Password: wap

Source: https://communityforums.rogers.com/t5/Wireless-Knowledge-Base/Rogers-APN-Settings/ta-p/410438

=== Simyo (Spain) ===

APN settings:
APN: orangeworld

Source: https://blog.simyo.es/simyo-configuracion-internet-wap-mms/configura-tu-movil/

=== SFR (France) ===

APN settings:
Name: SFR webphone
APN: sl2sfr
username: <empty>
password: <empty>

Source: https://assistance.sfr.fr/tel-mobile/utilisation-param/parametrer-apn-sfr-mobile.html

=== Sunrise (Switzerland) ===

Name: Sunrise
APN: internet
Username: <empty>
Password: <empty>

=== Swisscom (Switzerland) ===

Name: Swisscom
APN: gprs.swisscom.ch
Username: <empty>
Password: <empty>

=== Tele2 (Sweden) ===

Name: tele2
APN: 4G.tele2.se
Username: <empty>
Password: <empty>

Source: https://www.tele2.se/support/felsokning-guider/tjanster-installningar/mms-och-data

=== Telekom (Germany) ===

APN settings:

Name: Telekom
APN: internet.t-mobile
Username: t-mobile
Password: tm

Source: https://www.telekom.de/hilfe/mobilfunk-mobiles-internet/mobiles-internet-e-mail/apn-mobilfunk/wie-lauten-die-apn-fuer-mobilfunk?samChecked=true

=== Telekom (Hungary) ===

APN settings:

Name: Default
APN: internet.telekom
Username: <empty>
Password: <empty>

=== Telenor/Yettel (Hungary) ===

Voice based plan - both calls and data are included:
Name: Yettel Online
APN: online
Username: <empty>
Password: <empty>

Data-only plan - no calls, only data and SMS:
Name: Yettel Net
APN: net
Username: <empty>
Password: <empty>

IPv4 is preferred, as IPv4v6 is not reliable according to multiple Yettel customer service employees.

Source: https://www.yettel.hu/beallitasok/android

=== Telenor (Sweden) ===

Name: Telenor SE
APN: services.telenor.se
Username: <empty>
Password: <empty>

Source: https://www.telenor.se/kundservice/vanliga-fragor/min-mobil-surfplatta/vad-har-telenor-for-apn-installningar/

=== Telia (Finland) ===
Name: internet
APN: internet
Username: <empty>
Password: <empty>

=== Tello (USA) ===

Name: T-Mobile
APN: fast.t-mobile.com
Username: <empty>
Password: <empty>

MMS settings:

MMSC: http://wholesale.mmsmvno.com/mms/wapenc
APN: fast.t-mobile.com
Proxy: <empty>

=== Telstra (Australia) ===

Name: Telstra Internet/WAP
APN: telstra.iph
Username: <empty>
Password: <empty>

=== Three (UK) ===

Name: 3
APN: three.co.uk
Username: <empty>
Password: <empty>

=== Ting (USA) ===
Using the X3 sim card:
Name: Ting Data
APN: wireless.dish.com
Username: <empty>
Password: <empty>

For MMS configuration had success using:
MMSC: http://wholesale.mmsmvno.com/mms/wapenc

The article mentions using this APN for a hotspot, but unconfirmed
Name: Ting Hotspot
APN: tethering.dish.com
Username: <empty>
Password: <empty>

Source: https://help.ting.com/hc/en-us/articles/205428698-APN-setup-guide#android-apn-settings-with-the-x3-sim-card-0-1

=== Tracfone (USA) ===

''BYOP SIM Card Kit'' works with T-Mobile and AT&T compatible SIM cards provided in BYOP kit.

3G/4G data known to work with Verizon & AT&T SIMs (most likely works for T-Mobile as well).

Use the following APN settings:

Name: Tracfone
APN: RESELLER
Username: <empty>
Password: <empty>

To use Verizon's network:

Name: Tracfone
APN: TRACFONE.VZWENTP
Username: <empty>
Password: <empty>

MMS has worked with the following settings:

MMSC: http://mmsc.cingular.com
MMS Proxy: proxy.mvno.tracfone.com

=== T-Mobile (Czech Republic) ===

Name: T-Mobile CZ
APN: internet.t-mobile.cz
Username: <empty>
Password: <empty>

=== Verizon Contract (USA) ===

There are several APN names which can be used, for example:

Name: 4G LTE Contract
APN: vzwinternet
Username: <empty>
Password: <empty>

Other APN names which appear, and may work if the above does not:

vzwapp
vzwims

=== Videotron (Canada) ===

Name: Videotron
APN: media.ng
Username: free
Password: <empty>

=== Virgin Mobile (Canada) ===

Settings might work with Bell Canada too since it is the same network.

Name: Mobile Fast Web
APN: pda2.bell.ca
Username: <empty>
Password: <empty>

=== Vodafone (Czech Republic) ===
Name: internet
APN: internet
Username: <empty>
Password: <empty>

Source: https://www.vodafone.cz/pece/osobni-a-firemni/otazky/zaciname-s-chytrym-telefonem/pripojeni-nastaveni-internetu-v-telefonu/

=== Vodafone (UK) ===
Name: Vodafone
APN: wap.vodafone.co.uk
Username: wap
Password: wap

These settings work on 4G.

Ignore Default/asdamobiles.co.uk APN if present.

=== winSIM (Germany) ===
Name: winSIM
APN: internet
Username: <empty>
Passwort: <empty>

Source: https://service.winsim.de/help/showGeraeteeinstellungen (Requires login)

== Carriers that do not work ==

=== FreedomPop (USA) ===

VoIP-service. Customer service said they require Android 4.3+, and their free calling and texting works only with the Google Play app they make you use. So calls and texts don't work with non-smart phones and won't work with the PinePhone (even though it is a smart phone) because of software incompatibility. However, the data part still work if APN has been seen correctly set to '''fp.com.attz'''. You get 200MB free data per month. However, please watch out that you will get ding by $20 top up charge when over 200MB limit.

APN: <code>fp.com.attz</code>

=== Sprint (USA) ===

Sprint is currently not supported due to unknown issues, see also [[PinePhone Carrier Support#Sprint]]. Any input regarding this issue is highly appreciated.

APN: <code>cinet.spcs</code>

=== Visible (USA) ===

Visible does not have any way to approve unsupported phones, it might be possible through APN settings, but requires more research and dev time. Even activating a SIM using a supported phone, and then moving it to the Pinephone does not work.

=== Other ===

Other VoLTE services.

== External links ==

* See also https://forum.pine64.org/showthread.php?tid=9150
* LineageOS APN and MMS defaults - https://github.com/LineageOS/android_vendor_lineage/blob/lineage-19.1/prebuilt/common/etc/apns-conf.xml

[[Category:PinePhone]]

Overclocking

2023-03-18T20:40:51Z

PineMarten: Use the same codeblock style for consistency

{{warning|1= There is the possibility of damaging your equipment by overclocking. Do so at your own risk!}}
{{hint|This page is incomplete, you're welcome to improve it.}}
{{hint|All information regarding clock speeds, voltages and more are stored in the DTB (Device Tree Blob). You can learn more about it [https://elinux.org/Device_Tree_Reference here].}}

Overclocking is a way to get more performance out of the system by running it at higher clock speeds than the factory default, usually while putting out more heat and using more power (You can also downclock to possibly reduce power consumption and thermals at the cost of performance). It is highly recommended that you avoid overvolting the device, as that has a high risk of damaging the hardware, hence the warning at the beginning of this page. However, just some slight overclocks without the added voltage can not only improve performance, but not carry as much risk (Still: Do at your own risk!). It should be noted however that overclocking can cause instability, so you will need to test and see what values work best with your device (There is a silicon lottery for the Pinephone's hardware).

= A64-based devices =

{{note|These instructions are targeting the PinePhone to simplify the explanation, however they can be used to also overclock other devices such as the Pinetab if you modify the proper DTB files.}}

== Editing the PinePhone DTS ==

In order to overclock the PinePhone you will have to first convert the DTB file in <code>/boot/dtbs/allwinner/</code> to a DTS file. You will see <code>sun50i-a64-pinephone-1.2.dtb</code>, and also two other files with different PinePhone mainboard revisions (1.1 and 1.0). You will want to select the correct file for your PinePhone (Only choose 1.1 if you have a Braveheart, As all other consumer PinePhones use the 1.2 DTS).

Once you've found the file, you can run the following command to convert the DTB to DTS:

dtc -I dtb -O dts /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts

Finally, modify the newly converted .dts file and change the clockspeeds you wish to modify. You can simply use a text editor to do so.

To convert back to DTB:

dtc -I dts -O dtb /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts -o /boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dtb

Afterwards you can simply reboot and check with <code>sudo cat /sys/kernel/debug/clk/clk_summary</code> to see if the changes have correctly applied.

{{note|In the future it is possible that someone may make a driver to adjust clockspeeds of the A64 from userspace (using a config file) without the need to recompile. However, currently the only way to overclock is to either compile your own kernel, or modify just the DTB (instructions above).}}

== GPU ==

Open <code>/boot/dtbs/allwinner/sun50i-a64-pinephone-1.2.dts</code> (You will have to find the source of the kernel used by your distribution. There is the Pine64 kernel, and Megi's) in a text editor following these instructions: https://wiki.pine64.org/wiki/Overclocking#Edit_Pinephone_DTS

Look for <code>mali: gpu@1c4000 {</code> and within that block search for <code>assigned-clock-rates = <432000000>;</code>

The <code>assigned-clock-rates</code> line should be set to <code>432000000</code>, this means that the GPU is clocked at 432MHz by default. So if you want 500MHz, set the value to <code>500000000</code>.

Save the DTS file, and recompile the DTB. In order to check if the overclock was successfully applied you can run: <code>sudo cat /sys/kernel/debug/clk/clk_summary</code>.

{{note|The file may be slightly different and you may need to enter the values as hexadecimals}}
{{hint|The GPU appears to run stable overclocked to 540 Mhz, however more testing with a wider group of devices is needed.}}
{{hint|Remember to run a benchmark tool (such as glmark2-es2) to help check stability.}}

== CPU ==

The stock speed of the A64 is 1.152 GHz. The A64 can be overclocked significantly, it is highly advisable not to do this unless you can also drop the voltage at the same time.

If the CPU is undervolted and overclocked at the same time, it is possible to reach similar thermals and power consumption to the stock configuration but with better performance.

{| class=wikitable
|+ Power consumption at different voltages and frequencies
! Configuration
! Frequency
! Voltage
! Power (Screen 50%)
|-
! Stock
| 1.152GHz || 1.30v || ~4.35w
|-
! Stock + Undervolt
| 1.152GHz || 1.18v || ~3.65w
|-
! Overclock + Undervolt
| 1.344Ghz || 1.28v || ~4.60w
|}
The table above contains measurements created in postmarketOS (SWMO/SXMO - postmarketOS 21.12 SP1) with the screen on (set to 50% brightness) under a threaded load.

{| class=wikitable
|+ AXP803 PMIC voltage steps on DCDC2.
! Voltage range
! Step size
|-
! 0.50V-1.20V
| 10mV
|-
! 1.22V-1.30V
| 20mV
|-
|}
The table above shows the valid voltages provided by the AXP803 PMIC on DCDC2 (used to power the cores). For example, setting the voltage to 0.60V is valid, but setting it to 1.23V is not. When overclocking, ensure that you only use valid voltages at each operation point (otherwise it will simply be dropped and ignored). You can use (after installing) cpupower to display all valid frequencies after boot.

{{note|The user ''somefoo'' was able to undervolt the PinePhone at each frequency operation point by at least -100mv. The A64 set to 1.152Ghz runs at 1.18v instead of the standard 1.3v, dropping the power usage by ~0.7w under full single threaded load! The silicon lottery will dictate how well you can undervolt.}}
{{hint|The exact voltages and frequencies that you can achieve will depend on your device. Make sure to run stress tests (such as ''stress-ng'') to ensure stability.}}

== DRAM ==

{{warning|1=It is not recommended to exceed 667 MHz clockspeed on the DRAM. 648MHz is likely the upper limit.}}
{{hint|Make sure to set your DRAM to a multiple of 24.}}
{{hint|The current frequency your DRAM is running at can be found using this command: <code>cat /proc/device-tree/memory/ram_freq</code>}}

When overclocking the GPU, it is a good idea to also overclock the DRAM, as the main bottleneck of the A64 SOC is the memory. The A64's maximum ram clockspeed falls just short of 667MHz. This may be unstable on your device however.

Around 600 MHz (PC-1200) should work fine, however some people have reported instability at lower clockspeeds. Arch Linux Arm uses a default clockspeed of 552MHz, with U-Boot builds available to easily switch out for a higher (624) or lower (492) DRAM clockspeed.

It is possible that by reverse engineering the DRAM driver from Allwinner that auto tuning can be accomplished to get the best performance.

Setting the DRAM clock is accomplished by modifying pinephone_defconfig in U-Boot (https://gitlab.com/pine64-org/u-boot/-/blob/crust/configs/pinephone_defconfig)

You can find simple instructions on doing so here: [[U-Boot]]

== VPU ==

In order to allocate more VRAM for the GPU you can add <code>cma=256</code> to your kernel (or use kconfig with CONFIG_CMA_SIZE_MBYTES=256) cmdline in boot.scr which you will have to compile using mkimage. By default the kernel allocates only 64MB, and the maximum value is 256MB.

In order to compile boot.scr you can run <code>mkimage -C none -A arm64 -T script -d boot.cmd boot.scr</code>

{{note|You may not have a boot.cmd file in your boot directory and instead you may instead have a boot.txt}}

== Cedrus ==

Overclocking cedrus is achieved by modifying the kernel source code: https://elixir.bootlin.com/linux/latest/source/drivers/staging/media/sunxi/cedrus/cedrus.c#L507

{{note|User ''33yn2'' is not particularly sure if this makes any difference, or if it might in fact have a negative impact. Probably not worth messing with.}}

= RK3399-based devices =
The RK3399 clocks are found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-opp.dtsi]

More optimised voltages and clocks can be found in [https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi arch/arm64/boot/dts/rockchip/rk3399-op1-opp.dtsi]
These include a slight overclock and undervolt, they are intended for the OP1 CPU found in many Chromebooks but have worked fine in all recorded cases on regular RK3399 SoCs in other devices.

==GPU==
Any clock speeds can be added for the GPU in <code>gpu_opp_table</code>

The highest recommended voltage for the GPU is 1.2V as specified in the RK3399 schematic from Rockchip.

Segfault has found that the RK3399 in his Pinebook Pro can reach 950MHz on the GPU while being stable.

The stock speed for the GPU is 800Mhz.

Note that the GPU in the RK3399 is already bottlenecked by the memory bandwidth available to it, so overclocking generally yields no improvements.

==CPU==
A set of available clock speeds that can be added to the CPU clusters can be found in <code>drivers/clk/rockchip/clk-rk3399.c</code> under <code>rk3399_cpuclkl_rates</code> for the little cores and <code>rk3399_cpuclkb_rates</code> for the big cores.

These clock speeds can be added to <code>cluster0_opp</code> for the small cores and <code>cluster1_opp</code> for the big cores respectively.

The maximum limit is 1.8GHz on the little cores and 2.2GHz on the big cores.

The highest recommended voltage for the little cores is 1.2V and for the big cores is 1.25V.

Segfault has found that the RK3399 in his Pinebook Pro can reach 1.7GHz on the little cores and 2.08GHz on the big ones.

The stock speed for the little cores is 1.4GHz and on the big cores it is 1.8GHz, the OP1 speeds default to 1.5GHz and 2.0GHz instead.

= ROCK64 =

DTB is in <code>/boot/dtbs/rockchip/rk3328-rock64.dtb</code>. CPU clock rates are inside <code>opp_table0</code> as hexadecimal numbers in the <code>opp-hz</code> field.

Check the achieved clock speed with <code>sudo cat /sys/kernel/debug/clk/clk_summary | grep armclk</code>. Does not seem to overclock at stock voltages at all, defaults to 408 MHz if it fails to set a clock rate. Stock voltage is 1.30V, just shy of the 1.35V maximum outlined in [https://www.rockchip.fr/RK3328%20datasheet%20V1.1.pdf the datasheet]. Overvolting to 1.325V just left the device in an unbootable state for CounterPillow, would not recommend.

GPU needs investigating, but current mainline device tree does not try to clock up the GPU at all.

[[Category:SOPINE]] [[Category:PINE A64]] [[Category:PINE H64]] [[Category:PINE A64-LTS]] [[Category:Pinebook]] [[Category:PinePhone]] [[Category:PineTab]] [[Category:ROCK64]] [[Category:Pinebook Pro]] [[Category:ROCKPro64]] [[Category:Allwinner A64]] [[Category:Allwinner H6]] [[Category:Rockchip RK3399]]

Talk:PinePhone Pro/IMX258 Camera Debugging

2023-02-20T21:27:05Z

PineMarten: removed my section

Talk:PinePhone Pro/IMX258 Camera Debugging

2022-11-27T01:10:39Z

PineMarten:

== Megapixels sefault ==

<blockquote> After patching some trivial segfaults, […] </blockquote>

Would it be possible to upload a .diff with said patches?

--[[User:Thelie|Thelie]] ([[User talk:Thelie|talk]]) 10:25, 17 October 2022 (UTC)

== New rkisp1_csi entity in pipeline ==

It seems that as of July 2022, the kernel treats the CSI in the Pro as a separate media-ctl entity, adding rkisp1_csi to the pipeline.
As far as I can tell, the kernel documentation for rkisp1 has not been updated to reflect this.

I have spent some days learning about how these sorts of things work (no prior experience with csi or media-ctl), and I have linked my sensor to the CSI, and the CSI to the ISP.
After linking, the rest of the media-ctl commands (from the shell script provided for taking pictures) work, but v4l2-ctl reports a broken pipe error when trying to stream to "frame.raw".
Apparently, this can mean that the format is misconfigured for one or more pads.

Can anyone shed some light on this issue? I have tried a few combinations of links and formats and I feel like this knowledge should be out there somewhere...

--[[User:PineMarten|PineMarten]] ([[User talk:PineMarten|talk]]) 10:25, 26 November 2022 (UTC)