-
Content Count
5,864 -
Joined
-
Last visited
-
Days Won
372
Everything posted by EskeRahn
-
PRO1, LineageOS 16.0 Official Builds: Discussion
EskeRahn replied to tdm's topic in General Discussion
Good to know that it is not a thing specific to the Pro1, but a more general issue. -
PRO1, LineageOS 16.0 Official Builds: Discussion
EskeRahn replied to tdm's topic in General Discussion
Thanks for the info and link. and indeed the first green is on page 6 💚 -
PRO1, LineageOS 16.0 Official Builds: Discussion
EskeRahn replied to tdm's topic in General Discussion
Thee first weeks after it went official we got weekly Monday builds. But not the last two Mondays. I see a lot of pending stuff described here https://download.lineageos.org/pro1/changes/ Anyone knows what is preventing these from going 'live'? -
Let us hope for those preferring the keyboard in the wrong direction that this will be something less humongous that the Titan. The larger the variation the larger a target audience that can get what suits their needs.
-
I am by far an expert in this, though I have used some time digging into it. The first part of the quote is clearly right in broad terms, but it is actually more complex. If we are below 50% and the battery is at room temperature high currents are not a problem, it is when the battery get more filled up and&or the temperature rises that the high currents are problematic. On the second part, this sounds really confusing and against normal physics. I never heard of a charger overheating by supplying a low charge (On the contrary cheap ones can overheat while producing high currents
-
Well the answer is that to care for the battery as slow as possible - it is a matter of keeping the temperature at room temperature below 30°C. BUT it is not that it is killed immediately by fast charging, or a very sharp limit at 30. it is like fast-food: Occasional usage can be very convenient, but very bad for the health and overall lifespan if used daily. I have written a lot more on my blog with links. Start e.g. here
-
PRO1, LineageOS 16.0 Official Builds: Discussion
EskeRahn replied to tdm's topic in General Discussion
Interesting bug! Does this mean that sim1 is active bypassing the pin? Or 'merely' that both are deactivated (despite you only requested sim2 deactivated). Can you do calls/sms/mobile data on sim1? -
(merged threads)
-
If you (for whatever reason) got some severe issues, here a small guide. 1) The simplest one is to do a factory reset (Settings, System, Advanced. Reset option, Erase all data ), Make sure to save anything you need first!! 2) You might be in need of providing it with a clean new firmware image You can restore to a well known state, see e.g. this https://community.fxtec.com/topic/2466-guide-restore-to-stock-firmware-using-fastboot-method/ or https://community.fxtec.com/topic/2559-factory-restore-tool/?tab=comments#comment-37626 The first of these start at a r
-
I am utterly impressed 😇 ....But assume it is a typo. (But I do agree that it is frustration how the production again and again get delayed)
-
Thanks for the quote. Moved it to the 'locked' thread, so it will be easier to find for others.
-
Indeed odd, but could make some sort of sense as APN is related to mobile data. I wonder if this is a general Android Pie bug/feature, or specific to the Pro1?
-
(There is also an ubuntu port in a very early stage)
-
Well as it is not hardware detection that is the issue it must be software that is somehow messed up. And as no others have chimed in with the issue it will be hard to guess what it could be, but you could try to uninstall/disable/stop various stuff and hope you can find it - but I guess you easily will use even more time trying that.... That the keyboard backlight does not turn on, also indicates something is rotten, of course in theory it could be two independent failures, but seems unlikely. (I take it for granted that you in the Settings, Slider have Turn On Backlight set to on)
-
Then my best guess is a factory reset...
-
Yes, as you can see in the other thread the other one is for detecting e.g. a flip case, You can trigger that one with a strategically placed magnet, but it has nothing to do with the keyboard, So as the sensor works it seems like some software issue. What is the firmware installed on it? 2020-07-07?
-
Try the factory test described in this thread, The magnetic hal sensor is number six from the bottom, just above "OTG"
-
PRO1, LineageOS 16.0 Official Builds: Discussion
EskeRahn replied to tdm's topic in General Discussion
Just for info and off topic this is not LineageOS only, the same goes for Stock. Below an example from July 19th, with very little usage, where it dropped 10% in 20½h (red line) -
That is interesting. I use password or fingerprints for unlock, and does not see it on unlock. I wonder if it is a general issue when used 'unprotected' or it's some software you have installed that triggers the issue? We have had people reporting random boots most likely related to when a WiFi signal is seen as very weak. I wonder if what you see could be a milder version of that? Could you try to temporarily stop WiFi, and see if this has any effect on the bug.
-
Is this a temporary hiccup where it continues by it self, or does it hang so you need to force a restart by long holding the power button?
-
Something is clearly wrong if it reached close to 60°C. I would suggest to hear what Support has to say in the matter.
-
The odd thing is that if I in Stock settings search start to type "wi-fi-calling" it knows where the setting is supposed to be - it just do not display (It displays correctly on LineageOS) Stock: LineageOS
-
The one I currently use is this one. Do not get confused on the "2.1A" print it only delivers 1A - and this is exactly what I want from it *LOL*
-
PRO1, LineageOS 16.0 Official Builds: Discussion
EskeRahn replied to tdm's topic in General Discussion
Try something like adb shell settings put global sms_outgoing_check_max_count 99999 adb shell settings put global sms_outgoing_check_interval_ms 9000 It is a silly default set way too low IMHO.... Note that is is counting the INDIVIDUAL SMSes that is roughly each 157 char for plain A-Z type, and 67 chars if at the least one unicode char is used. So a lengthy SMS sent to a several friends (bulk not chat) can easily hit the default ceiling, -
Unfortunately QC chargers does not come with a simple switch to select normal or quick charge (I have not found one yet). BUT you can easily find QC 3.0 chargers with two or more slots, where only one is QC. This is a very handy thing. Use the normal slots normally and only the QC3.0 one when you are really in need of it. See also this I use one found on ebay that provides 5W in two slots and 20W QC3 in the last one. it is 2.5cm thick, and 5x5cm excluding plug (85mm including EU plug) so not much bigger than other chargers.