Leaderboard

I had 2 random reboots when I was visiting my friends at another city (different location). However, I haven't faced any random reboots when I am staying where I currently live. So I believe that the reason for random reboots could be different network. This might also explain why @ddark-il is facing reboots on specific train. Maybe the network is changing during that train trip?

My phone also rebooted 10 times a day, but I found a solution. I turn off wcdma network in settings and after that the phone becomes stable. So try switch preffered network types.

You should quickly buy stock in Aukey, before @EskeRahn buy's all their ultra ultra slow chargers. 🙂

Hi, I am from Hong Kong. I know most of the city in China will return to work until 20th Feb. Also, most of the check point of Hong Kong are closed. There is only one land transportation method can be used to ship the stock. It is very disgusting that the Chinese Gov conceal the news about the virus. When you get the phone, PLEASE DISINFECT IT. More than 10k chinese is infected. Absolutely 10k is the number released by Chi Gov. I believe that the actual number is far greater.

That's why i'm asking about the mic and hall sensor (aka keyboard open/closed sensor), those connect trough the same cable. The same board also routes signal to an antenna (for wifi if i remember correctly) but for that it connects to the mainboard via a different cable.

Aha, resizing in portrait only seems to work if display size is set to small in Android Settings. It doesn't work if set to default. Annoying that it only allows three split ratios (roughly 30:70, 50:50, 70:30), rather than allowing a free choice.

You all know that the phones are assembled with gloves, facial masks and some kind of hair protection? Yes, the virus can survive that long in special cases. But if production was that unhigienic, you'd have hairs, fingerprints and saliva on your phones when receiving it. Also, if it was a threat, international trades would already have been prohibited.

Yes that is what I wrote: Android Market , http://market.android.com/ ...I know i'm old, but I'm not going to use the silly alias

I pretty much think your prayers have been answered, as the app does work in that way, I'm sure. It does have a so called "Pocket Mode" which is described in the documentation. It doesn't behave like when your making a call. In that instance the phone isn't locked when you put the device to your ear and the developer has taken that on-board so WaveUp doesn't lock the phone while a call is in progress. As for the aforementioned battery drain, I haven't noticed anything untoward. You can set a xx second warning which gives a short vibrate xx seconds before the screen turns off and locks. You

It does really sound like a bad USB port... Did any other issues occur that you noticed like software keyboard always coming when a textbox is selected or not working atall, or microphone not working atall? (the board that has the USB connector also has the hall sensor to know whether the keyboard is open or not and a microphone)

Probably best to have phone turned off while opening front cover anyway. sorry, sarcastic comment cuz I can't imagine what front cover you're opening

...AFAIK at least one of those cases has been posted earlier in this thread. Also, if they're anything like the 'universal' case I found, they'll be annoyingly larger than the Pro1.

Shift will only work for capital letters in that case. Not for anything on the number row for example.

Sorry for not being specific. I wasn't happy with the FinQwerty layouts. In another post, someone had mentioned it's possible to restore functionality by disabling all of the keyboard layouts. Sounds counterintuitive, but if the keyboard input profiles are all blank (deselect all of the profiles and then hit the back arrow) the phone will go to "default". All of the keys, shift, and special characters will work. See my attached photos. There will be a notification prompt urging you to select a keyboard input profile. You can tell Android to silence it which is what I did by swiping

It is known bug on few devices. I got wierd way to replicate it - it always reboots on specific train. Already sent bugreport data to Waxberry. If it's too annoyingfor you, you can revert to OTA version before SafetyNet(can't remember the exact build, but it was ~8MB), it still reboots, but much less.

This will take you to a poll which includes the fxtec pro1 as one of it's options. Let's make this happen.

Speedtest also works fine on mine. And I did the ADB thing to allow charging when turned off, but I am not currently rooted, stock firmware. My BL is unlocked as it came to me that way and I have never changed that.

No. As I said, it can be minutes after booting, with wifi completely up and running. This isn't related to the ping latency issue. Well, not unless it is somehow. lol

F(x)tec didn't think real hard about searching when they used parenthesis in the brand name and superscript in marketing name.

Munich, Germany

Taiwan, Kaohsiung

That is also what I thought but I could not find any applications that I thought it may affect it... Also we are on the latest OTA...

Didn't see it in the list, so Telus (Canada) working with no issues. 4G, calls, SMS, MMS, other data, all good.

Thanks for making me aware of this! That's why I thought it simply didn't work at all for me, nobody said it no matter how furiously I googled, only that it's supposed to work in portrait mode only. I only ever tried resizing a little bit, not expecting Android to be quite as crappy as it is 😂

If he has root you can try if the LEDs work from terminal, first make sure you are root by running 'su' and then: echo 255 > /sys/class/leds/red/brightness To turn the LED fully red, change red to blue and green in the path to set brightness of other colors. Values for brightness are between 0 and 255, you can echo 0 to all 3 colors to turn the LED off. If that works for all colors at least you can know it is not a hardware problem.

It is in the official Android Market too https://play.google.com/store/apps/details?id=com.jarsilio.android.waveup

My Pro1 has habit of spontaneous reboots once or twice a day (running stock), and I'd like take a stab at figuring out what is going on, so I'm trying to figure out if I an get at any logs from prior to the crash. I've looked for stuff like /proc/last_kmsg and /sys/fs/pstore/console-ramoops running 'dmesg' just gives a permission error. Anyone know what the right method would be? Is it possible without root?

@Waxberry Any updates on the situation already? Excuse me for being a bit pushy now, but I'd hate if this went off your mind over the weekend or something and I only noticed I should've brought it up again later. As I'm expecting multiple days of turn-around on FedEx' end, I'd love quickness where I can perhaps still influence it a bit. Having the package find it's way to me this week would be cool. I'm calm about it, but also kept seeing that some parties have to be asked again to actually get responses for some reason (lost like a week of time from that)... well that's for FedEx, but

Thanks for the link. Using that Sensors Test application it looks like our light sensor is just left of the ear piece speaker.

Yes, I got that. My point was that it would require a hole for the earpiece, unless you slide it 1cm up during calls. On the last part I would consider to mount it in a £1 clear silicone shell, and then let that be attached to the case.

...Looks interesting, but before I use it does the Pro1 suffer from this issue at all?

Minsk and Vitebsk, Belarus

Slovakia, Zilina

Sorry Craig, I'm totally confused now. We want Shift to be the button that calls up special characters instead of the yellow arrow? If that's the case, then I'm just going to sit quietly in this corner. Just ignore me. My bad guys!

USA, Washington, in Seattle

From what I can tell it's left of the front-camera. You can try a diagnostic app (built-in), described in the following post: This helped me figure out where the sensors were and if they work as expected. Be careful with the settings and do read that specific post in full before doing anything.

So.. after having someone properly glue my screen to the pro1 (I apparently did not do it right), I do experience some rattle when moving the screen top-to-bottom and vice versa (in closed state). It is not as annoying as the thread author states, but it is there. Still works great, though.

He's mistaken. If you have finqwerty layouts installed, you can use them. The layouts included with stock (besides german for qwertz) don't use the fn-key at all, so the only way to get slash and question mark on qwerty is to not select any layout at all - but then shift won't work right, so finqwerty is a better solution anyway.

Using mkbootimg can be confusing and frustrating. I use a script to repack boot images after modification: repackbootimg It expects the files created by unpackbootimg to be in the current directory. It also can repack the ramdisk if it is extracted under a directory named initrd. Something like the following will do this: mkdir initrd cd initrd cat ../boot.img-ramdisk.gz | cpio -id cd ..

I've used this tool with success to modify both stock and lineage boot images: https://github.com/vianney/bootimgtool bootimgtool -x -v qcom To extract, and then to repack it, if i recall correctly: bootimgtool -c -v qcom -p parameters.cfg -k Image.gz-dtb -r ramdisk.img To replace the kernel I stole the DTB from the kernel in a boot image with https://github.com/PabloCastellano/extract-dtb and just used cat to append only the first one of the extracted DTBs to the new kernel (only that one appears to matter at all).

Looks like there's one upside to my package being stuck in customs.

I can reassure you: transmission by objects is not possible in practice due to the fact that the virus has very little stability on surfaces. Especially if the objects were on the move for longer. Source (German): Link.

I've done some research and this problem seems to occur rarely but I haven't found any fixes. Some users report that the problem appeared after months of using the feature. It may sound stupid, but have you tried turning it off and on again? If that doesn't help, you could delete cache and dalvik cache and if that doesn't help either, you could restore factory settings, but this should be the last step. Edit: With Android 10 resizing is also possible in landscape, so don't lose all your hopes.

The main part of this is you have to boot to bootloader before executing this command. From android, you can execute adb reboot bootloader; I think you're sfos, so you're stuck using the voldown+power method to get there which always works.

Was looking for an app that could activate the screen when opening the front cover (like on my XPeria X, which uses a magnetic sensor). Found WaveUp on the F-Droid Store. The app uses the proximity sensor and works excellently in both portrait and landscape. https://f-droid.org/en/packages/com.jarsilio.android.waveup/

Let's try to get a list of the USSD/MMI codes our phones support. For example, I was pleasantly surprised with *#06# When you enter this in your dialer it will present most of the information from the sticker we have on the back of our phones. This code is kind of universal and works on majority of devices. I am more interested in discovering Pro1 specific ones, though :) *#*#0000#*#* - Hardware information (like platform model, IMEI, etc.) *#*#4636#*#* - Brings an extensive testing application that gives lots of info about networking and app usage *#*#2432546#*#* (*#*#check

When delays start to be this long, you are bound to be hit by factors that are not under your control. Not that it changes anything, but it's 6 months since payment was due. I just wonder for how long can a company survive with such delays. In tech world, in half a year not only does your hardware grow older faster, but it also kills all future sales if you cannot provide the product 2-3 months after the general availability should have started. Not that I care about the specs personally. I'm still using a phone from 2012.. On the positive side Sailfish port will get better day by da

Same here! Mine doesn't rattle in open position. Only noise that I can hear comes from flat cable (in closed position) and SIM tray. I am very satisfied about the quality.

Sure. To access the factory test tool (within the stock rom of course), enter Settings -> About Phone -> Anroid Version. You will be presented with a popup, scroll down there and tap 3 times quickly on the build number: The options below are proximity- and Ambient light sensor test. To you and others: be careful with the others. One option dials emergency without any further warning! The two matching tests are checked on my screenshot: edit: You ninja-edited your post. have you tried turning it off and on again?

Contractual, I believe, since it has a remote root access on your device so that it can install/update any software/firmware it needs/wants to, that's its actual purpose as a FOTA. From what I understand, it is also purposefully meant to also have spyware functions if needed for device manufacturers in countries (or companies) in which regulations either do not forbid or require the presence of this kind of malware. I don't think any of us is actually arguing that this is not potential malware, just that F(x)tec is paying extra for it not to be (or maybe it's the opposite and F(x)tec actually