VaZso
-
Content Count
1,633 -
Joined
-
Last visited
-
Days Won
105
Posts posted by VaZso
-
-
1 hour ago, EskeRahn said:
Looking for other phones with same chipset we got this list on gsmarena
I tried googling for hdmi and one of them (the motorola G30) but found nothing. I did find a fairly officially looking answer suggesting using casting instead, so that sort of points toward that the chipset might not support it, and thus the link I first found could be wrong....
I remember when F(x)tec has announced the chipset change, there were some users complaining about the lack of external output by chipset.
...then F(x)tec told they have received a comfirmation about the chipset supports external display.However, I don't know who told this information to F(x)tec and if that info was true or not...
-
2
-
-
12 minutes ago, phoebus2000 said:
I know, another day another problem with my pgone.
Hdmi out does not work for me - I plug my adaptor into my Macbook and it is fine and displays, plug it into this phone and nothing. Tried a reboot and no good.
Anyone else have this problem?
Which phone do you have?
Pro1 or Pro1X?Pro1 supports HDMI out but not with its initial firmware (it was started working after an upgrade later).
Pro1X apparently does not support HDMI yet, hopefully they will solve this problem in a later software upgrade.-
1
-
-
10 minutes ago, phoebus2000 said:
Tried a factory reset. Contacted Fxtec a month ago and still no response. Emailed again 2 days ago asking for help or a refund as it turns out my phone isn't even connected to the phone network - when my wife calls it just says the phone is not connected.
I realise that this isn't related to GPS but combined with my network and Bluetooth problems I suspect something is faulty. Only response has been "we are aware of some connection issues" which is no good to me if I can't use a phone I paid a small fortune for and waited years to get.
As I said earlier I tried a factory reset and nothing changed.
It seems to be a common problem with Pro1X which I hope can be fixed by a software update later - maybe that is also the reason you have not received a reply yet... a potential firmware upgrade may fix the problem but they may not know when it is expected or if it can be really solved by a firmware upgrade...
-
1
-
-
43 minutes ago, unknown_death said:
Recently my
Recently my Pro1's finger print sensor started overheating and burns to the touch and is draining my battery quite significantly
I think it is harder to obtain that part but it worth a try to ask if F(x)tec has spare items.
Otherwise, I would pull the ribbon cable of the sensor - that way the phone itself would remain usable without excessive battery drain.However, it needs opening the bottom part of the phone - the worst part of assembling/disassembling of the phone is the ribbon cable of fingerprint sensor anyway as that is the cable what users can easily break in case the lack of attention.
-
2
-
-
2 hours ago, unknown_death said:
Hey everyone,
I am looking to buy a broken Fxtec pro1 to use as parts of you have one please let me know.
What is the problem of your Pro1?
F(x)tec also seems to have some spare parts. -
4 hours ago, xhajt03 said:
Slightly related - I had issues with FxService effectively disabling FinQwerty layouts on my Pro1x (only the default layouts worked correctly, FinQwerty layouts behaved as if I had the default stock QWERTY selected). I reported the issue to @Slion (the author of FxService), but he probably couldn't have analyzed it in detail due to only having Pro1 and not Pro1x.
I have recently ran into a similar issue on my Pro1.
I have installed AnyDesk which has installed a service and I had no FinQwerty-like layouts working until I have found that application was the cause of my issue and disabled its service.(Pro1, LineageOS 18.1 here.)
-
1
-
-
3 hours ago, EskeRahn said:
Well one unit, but composed of an elastic mat (rubber, silicone, ...?), with hard keytops on top, and a plate with holes around the keys.
That case I would glue it back to the mat (but not to the white thing below the mat - that was what I tried to express). 🙂
-
1
-
-
1 minute ago, JECE said:
That picture must be of the Pro¹, not the Pro¹ X. My keyboard layout is different. Maybe that's why we are having trouble understanding each other.
Basically that part should be the same except the print of the keys (layout difference is only a difference of printing).
2 minutes ago, JECE said:But EskeRahn seems to have it right. If you lifted the black keyboard in your picture, would the keys fall out? Or is there something squishy below the black keyboard, out of sight of the camera?
I didn't examined the keyboard precisely but no, keys don't fell out, black keyboard is generally one piece of material.
However, it may happen you have a key removed from the base of black keyboard material and it did not come out fully from it (leaving a hole in place).So I saw a keyboard pad which had a sticky bottom and there was a white part at phone base where keyboard was glued to using that sticky bottom (it feels similarly to a double-sided adhesive tape which does not have a cellux holder)
-
11 minutes ago, JECE said:
There is no foil, and there is no double-sided tape. There is just a faint speck of what I assumed to be some type of glue that held the key to the rest of the keyboard. I just need to know what type of glue that speck was.
There also appears to be no need to disassemble the keyboard. Even if it were necessary and I had the technical capacity to do that, how could I line the key up perfectly? Right now the key fits perfectly.
Is there any hope that a representative from F(x)tec will step in to provide guidance?
Look at these parts:
There is a white "foil" near the bottom-left corner.
That should be at the phone side and it should be intact.Above it, there is the keyboard itself which you have a missing key as far as I understood well.
That (black) keyboard has a double-sided tape at back, so its bottom is sticky (you can remove it using some heat).So I would try to fix the missing key in the black part and not gluing to the white part which should be kept intact.
Edit:
When I have disassembled my Pro1 the first time, I have also removed springs (it was not a good idea but I could put its assembly back) and keyboard mat (which was also not a perfect idea but I was able to re-align it perfectly).-
1
-
-
25 minutes ago, JECE said:
I'm not sure if I understand your question, but pressing [Z] works fine without the [Z] key. It's just a little more recessed without the plastic key, and with an annoying backlight. What's below is flat, firm, soft and translucent.
Basically keyboard mat should be one piece (all keys on one plate) which are glued (using doble-side tape) on top of button mebranes covered by a foil.
I would not glue it using a super glue as it will stick on top of the foil which covers the membrane so it will not remain in stock condition.
If you remove display assembly, keyboard mat can be removed by applying some heat using a heat gun and some mechanical help using a tool.
After removing mat, I would try to fix the missing key somehow - maybe using a sticker which has relatively strong adhesive (it should be elastic and that is also why super glue is not good for this purpose).
Also, this way you keep the option of replacing your keyboard mat later when F(x)tec will has replacement mats available.-
1
-
-
2 hours ago, Hook said:
Joke aside, if they authorize you to send it in, you are likely to get it back within a month, depending mostly on how many other repairs they have. They have spare parts right now. if needed, so they will fix quickly and return. The first time I needed a repair on my Pro1, it was a month including travel to and from London (from US). Second time, I knew I had to wait months for parts, but when parts were available, they had repairs done in 2 weeks.
It depends on what the problem is.
At first, I would think the UFS / flash IC may failing which most probably means a mainboard repacement would be needed... or if not replacement, a replacement of a BGA part of the mainboard which does not seem to be an easy task if we are speaking about a replacement mainboard of Pro1.
However, strange things may happen - I don't know how USB panel has caused unbootable phones (except triggering EDL mode by a failed connection), so who knows if it may cause other problems as well...
-
1
-
1
-
-
7 hours ago, Rob. S. said:
Looks like I don't get any more IGG updates through email, either, but that's easily explained by my IGG order (except for the spare battery) having been fulfilled in the meantime, other than my earlier Pro1 website order. Updates for website orderers have traditionally been less frequent...
I am receiving IGG udates (and I post it here if it is not already there) - my Pro1X order is already fulfilled, however, I have a separate "Enthusiast" order which has shortly disappeared from perks but it may happen that is the reason I am still receiving these updates.
-
2
-
-
6 minutes ago, itchy355 said:
I would gladly try that one. Thing is I can't find LOS 18.1 recovery boot.img anywhere. You specifically state that 19.1 won't work; could you perhaps up it to some google drive or whatnot?
I have uploaded recovery of last official LineagaOS 18.1 here.
-
2
-
-
6 hours ago, suicidal_orange said:
You're right - first thing in the morning I "only" saw two U keys on the Hungarian keyboard when really there are 4! Looks like two of them are on the wrong side of the Pro1's keyboard but at least they're not hidden behind the yellow arrow (Shift+Arrow+[key] is not thumb type-able)
The QWERTY version of Pro1 had a modified keyboard layout where non-alphanumeric keys were arranged differently (like "\", "[", "]", "`", etc), this is why we called it shifted QWERTY.
As I did not like this mixed-up keyboard layout and in Europe, I had an option to order my Pro1 with QWERTZ layout instead, I went to that direction.
So QWERTZ layout of Pro1 is closer to a normal QWERTY keyboard than its shifted QWERTY version itself.If we are speaking about Pro1X, F(x)tec has dropped this shifted QWERTY solution and went for standard QWERTY instead, so it is much more international having all keys in the right place and there is no need to re-train yourself for shifted QWERTY positions.
So, these characters are no longer in wrong positions, however, as far as I remember well, there was a character which was missing - I think position of "Ű" alias upper-right "\" does not exist while position of "Í" alias lower-left "\" exists - and it also explains why that button was skipped and why shifted QWERTY was a bad idea for multilingual use.
So Ű (scan code of 43) and Í (scan code of 86) looks to be identical using US layout ("\") but still have different scan codes and they were used differently on international keyboards.6 hours ago, suicidal_orange said:(Shift+Arrow+[key] is not thumb type-able)
This case I use "Caps Lock", then yellow-arrow + char, then "Caps Lock" again as yellow arrow is not sticky and it cannot be sticky if it remains hidden for OS (however, I don't know how simple is to have a further sticky modifier in case yellow arrow were not hidden).
I rarely have to use this double-caps lock thing as accented starting characters of sentences are statistically lower than not accented starting characters. 🙂
6 hours ago, suicidal_orange said:I'm hoping to use Ubuntu on mine so no idea what the keyboard options will be, your work sounds promising so I may well ask for a copy 🙂
I am using a modified version of Finqwerty which basically means I have added a custom descriptor file and removed its original layouts, then renamed it slightly but that is a high-level (Android) solution.
Also, I use a US-based layout and reaching accented characters using yellow arrow and their positions are also different than standard layout. 🙂
However, under Ubuntu, you will have a kernel module for keyboard handling (most likely the same module what was written for Pro1) and you may write your own high-level keyboard mapping using Linux tools.
Under Debian (on my notebook), I am also using a bit modified layout with the help of xkbcomp...Otherwise, modifying the keyboard module to expose yellow arrow would be very easy, simply it does not worth doing it only for yourself and managing to be built every time a new kernel may arrive, that is why I wanted to add that feature in official build (I don't need different hardware layouts of yellow arrow at all but a modifier key would be important).
I didn't think I will not be able to explain its importance to be understood and it will not go through because of the different conception of arrow key, even though they would have been live together as an optional feature.However, I have not looked into that code since then at all to see if it was implemented so far, but I doubt - I was tired of it.
-
2
-
-
2 hours ago, suicidal_orange said:
I thought it should be, and I see no reason they'd reinvent the wheel for the X.
They haven't reinvented the wheel - kernel module is handling the keyboard matrix through an IO expander IC (aw9523b) and reporting keypresses to kernel.
Most of the keys are handled through that expander while there are a few modifier keys which are handled directly - it is important because matrix arrangement also causes problems decoding multiple keypresses at once.2 hours ago, suicidal_orange said:It depends how you define a layout - if I want to put backspace on caps lock (great on a full size keyboard, not so much on a phone) that's not a language-layout which should be handled by the OS but it is a keyboard-layout.
There is a physical layout what kernel module handles (assigning scan codes to keypresses) and a logical layout which assigns scan codes to letters / numbers /etc.
When I have switched to LineageOS, I had some confrontation about what features the kernel module should have, I have even modified kernel module and some Android parts to show what I am thinking of... some of the ideas were programmed but as far as I know, some are still missing, like I wanted the yellow arrow key to also generate a scan code (as similar keys usually do on a regular PC, allowing the higher level OS to handle these functions) but the basic idea was an option for yellow arrow to generate completely different scan codes and handling it similarly as an Fn key was out of scope (also as an option).Finally, two interfaces of kernel module were built - one is the scan codes of regular keypresses and the other is the scan codes of key+yellow arrow keypresses.
(These can be loaded to kernel module through this interface in sysfs.)
As far as I remember well, an option for generating scan codes of pressing yellow arrow was never implemented in official LOS driver although that was why I have started modifying kernel driver and my demo had that feature... I have completely gave up working on keyboard module at this point (also I mostly regretted I have even started doing anything inside).At my side, I have modified Finqwerty for my custom layout in order to use accented characters - that was working well using stock OS of Pro1 but it was not working well using LOS and that was the reason I have started digging into lower level parts...
Now I am using a custom Finqwerty on LineageOS which works well anyway using latest version of kernel module.3 hours ago, suicidal_orange said:Double/triple/quad tap for all Hungarian "U"s on one key would need to send two different keycodes in standard and shifted states
Basically pressing a key should send a scan code to OS and OS should find an appropriate key for that code - that is what keyboard layouts do.
For example, a Hungarian keyboard has 0123456789Ö at top row while US keyboard has ~1234567890 but top row of keys are still producing codes of 41,2,3,4,5,6,7,8,9,10,11.
So scan code of 11 produces 'ö' if you are using Hungarian layout but produces '0' if US layout is in use.
If shift (scan code of 54) is also pressed, then it should produce "Ö" sign using Hungarian layout.Using standard layouts, ü,ű,ú keys are definitively having different scan codes (as these are independent keys of the keyboard).
If someone wants to produce them while pressing Fn+U, FN+I and FN+O, that should be handled at OS level, that is what keyboard layouts do --> it assigns a key (like ű) to a specific scan code... that way any letters (independently of upper/lowercase) may have different scan codes associated.Instead of this, Pro1's LineageOS driver handles Fn internally, then associates a scan code described in its internal hardware layout and solves the same problem at "hardware level"...
Both solutions have a reason... while the former is the standard behaviour, a program may still handle keypresses using low-level scan codes while this can be eliminated using different hardware layouts in low level (kernel module) - that was the original idea of Pro1's LineageOS driver.
Mostly games or similar software may use low-level key handling while most of user applications are working with the result of software layouts, so also having a scan code for yellow arrow would be more important for custom national software layouts anyway...Otherwise, I had the very same problem with writing áéíóöőúüű characters and I am using a very non-standard key arrangement. 🙂
3 hours ago, claude0001 said:As far as I am being told, that is a high level Android feature though, and has nothing to do with the actual device driver ("qx1000.c").
Right, that is an Android feature.
-
1
-
-
1 hour ago, suicidal_orange said:
Is the keyboard driver open source, or at least documented?
The keyboard handler code (kernel module) for Pro1 of LineageOS is open source.
I doubt they have changed anything related in Pro1X anyway (I mean in hardware)....but that is the low level handling code which has nothing to do with layouts (except it has a feature to export different key codes on pressing yellow arrow for example) but it is also not necessarily the same code used in stock OS of Pro1X.
Otherwise, after having appropriate key codes for key presses, layouts should be handled in OS level (Android part).
-
2
-
-
3 minutes ago, Acurus said:
This is an official Fxtec-Forum. And here is the production thread. I did not buy my phone via IGG. Therefore I asked here in the right place. Possibly somebody has some new informations about that, what is going on since some weeks. Today is day 14 since Fxtec declared, they stopped shipping. They declared, they finished the production of batch 1 and 2 (what ever this exactly mean). They sent some phones out. The rest is in the "warehouse". And since weeks nothing happend. This situation is very unsatisfactory, I ordered in May 2020 ...
I doubt anyone of us has further information about anything happens in the background - we are also waiting for an official information.
What @Hook has tried to tell this forum was created for communication between users and official staff may not necessarily reading threads here, however, they wrote in this forum time to time.
Basically this thread was initiated independently of official staff as a user to user base of information sharing about production and delivery.What I can say is they have really started delivery (I have already received my Pro1X).
I hope they will write an update soon then we may know further information.
-
1
-
1
-
-
1 hour ago, EskeRahn said:
And if you look at the size of the grid the keys are in (that is including the space between the keys) it is roughly 6x9.6mm
They Slim's keys are neck to neck sidewise. They are 6x6.2mm in a 7x6.2mm grid, so slightly higher grid, though the width is 35-36% less on the Slim....and this is a Nokia N900 near a Pro1X.
That has a key size of about 6x7mm and keys are neck to neck in every directions like a grid which makes it strange for first look.
Also the number of keys was much smaller - still it was a very useful keyboard (and Maemo was a really good OS by that time).
-
1
-
2
-
-
Not highly precise measurement but a usual key of Pro1(X) is around 5x8mm as per my measurement.
Top row is about 4mm in height....but I suggest you to try a similar keyboard in real life instead, as keys are much smaller than your thumb but still you can feel them accurately.
Also, Nokia N900 had similar keys (a bit smaller size) which was still a good keyboard.So it is not easy to decide if it is too small prior of trying.
Also, a bigger problem may be the phone (thus, keyboard) width [landscape] which may lead to some inconvenience if you have small hands (smaller than usual).
-
3
-
-
1 hour ago, Hook said:
I don't think this update was sent out as email at all, probably an error. I didn't receive it either and I have always had them by email. Always a good idea to check IGG once a week for new updates.
That is why some of us put these updates also in "state of production and delivery" thread here.
-
1 hour ago, Benni said:
Update: I just got a customs invoice from FedEx and the value of the phone is set to a larger amount than what I payed. Need to complain to FedEx about that.
I had a similar problem - payed in EUR through Curve which has deducted in HUF, but received an invoice in GBP.
These currencies have moved against each other in the last two years, especially HUF, but I sent them every related info and declared the amount deducted from my HUF accountFirst they told me in their first reply that my declared value is not even close to the value declared in invoice and in shipping note but I have explained the two years difference, originally deducted amount and F(x)tec's location of UK (regarding their declared currency).
So they have finally accepted the value declared by me which was the actual deducted amount in HUF.
Although the situation may not be clear, it seems it is possible to be solved in a correct way.
-
2
-
-
7 minutes ago, Ivaylo Hubanov said:
You mean it's not just mine, and we all suffer the same?
I haven't tested these things deeply but I had phone calling problems when range indicators were good and I also had two x near my SIM card indicators.
As far as I read, there is a beta firmware which already has some improvements, so it may be a matter of time...
-
2 hours ago, xhajt03 said:
Hello Logan, do you have any update on this? I see that the linked case design was for Pro1 rather than Pro1x. I wonder if all the controls, sensors, etc. are exactly the same size and location on both models (otherwise some updates would be necessary).
Basically sensors and buttons are at the same positions, only camera has a small difference (camera of Pro1X is out a bit by design).
-
1
-
-
4 hours ago, Ivaylo Hubanov said:
Any advices are much appreciated...
Unfortunately, firmware has to be polished, so my advice is to wait for a firmware update which may improve some of the problems...
-
4
-
Fingerprint scanner coming loose
in Support
Posted
I don't know what type of glue he used, but if I want to use a strong (and hard) glue, I use a two-component glue like DevCon (made in the USA) which is really strong and S-31 is water-clear but advised to be used in a well-ventilated place or maybe Uverapid for example (made in Hungary) but that is not 100% clear...
Basically these are two-component "epoxy resin"-based adhesives which are usually very strong glues.
DevCon is my favourite being really strong, has a long shelf-life and remains usable even long time after opened (if you not bought it from old stock).
S31 has an about 30 minutes of working time and it needs about 8-12 hours to cure or S208 for example has a bit less strength but only 5 minutes of working time and needs about 1 hour to cure.