Welcome, Guest. Please Login.
Linuxslate.com Forums

<=== Back to the Linuxslate.com Homepage

Jul 23rd, 2017, 5:57am
News: Welcome to the linuxslate.com forums. 16 Janruary 2015: Forum registration has been disabled due to recent advancements in bypassing captcha's and the resulting increase in spam on the forums. Registration will be re-enabled at a later date. In the meantime, if you need to register, or have relevant information, please email "john" at this domain, or request an account using the linuxslate.com Google+ Page: https://plus.google.com/+Linuxslate/


1  Original Projects and Builds / NodeMCU IoT Clock / Re: NodeMCU IoT Clock Status Update
 on: Mar 15th, 2017, 12:26pm 
Started by Administrator | Post by Administrator
Update and Serious bug notice:
 
--- Daylight Savings Time Errors:
11 March 2017 DST change did not work correctly due to glaring errors in the DST related code.  
   Spring Forward and Fall Back tied to wrong dates. Spring was in November, and Fall was in March.   embarrassed
   Other not - as - glaring errors and optimizations in this section of the main code.
 
-- Another DST related error in the Daytime connection to the time server.
   2 issues caused the initial connection to the Daytime server (port 13) and determination of whether DST was in effect to fail.
 
There seems to be another error causing cross talk between the settings for DST and 12/24 hour time display.  More research on this bug (if it actually exists) is needed.
 
I hope to also come up with a work around for Issue 1 mentioned in the previous post.
 
 
Reply Reply Quote Quote Notify of replies Notify of replies  

2  Mobile Linux Devices / Chuwi Hi12 and Related Tablets / Re-installing Android using a Linux PC (host)
 on: Feb 14th, 2017, 8:40pm 
Started by Administrator | Post by Administrator
Working with the Chuwi Hi12 from a Linux host is easy!
 
NOTE: What is below should work with other similar Chuwi tablets, such as the Hi10 and Hi8, but please make sure you have the correct firmware for your Tablet.
 
WARNING: What is below is for Chuwi Hi12 tablets that were Factory Capable of dual booting. This may not work, and may permanently disable older versions of the Chuwi Hi12 that were originally sold with Windows only.
 
WARNING: What is below will Delete all Partitions and Delete all Data -- Android and Windows.  It will delete Windows and All Data even if you do not intend to remove Windows. Even if Windows is working, you must backup all data in both OS's.  Deleting Windows is necessary due to the way the EMMC is partitioned from the factory, not because this is a Linux web site.
 
NOTE:  What is below does not flash the BIOS, so it is relatively safe given the above Notes/Warnings are heeded.
 
The following instructions work for the following cases, and may work for others.
1.) You want to erase Windows, and use Android (or possibly Remix) only.
2.) You have damaged your Android partition (Android no longer boots, wether Windows works or not)
3.) You have installed Ubuntu or another os, and altered or deleted the factory partitions.  As long as you can boot into the BIOS, what is below should work.
 
What You Need:
 
-- A Chuwi Hi12 Tablet -- Obviously -- We call this the "Target"
-- A Desktop or other computer running Ubuntu 14.04 or 16.04, or similar Debian Based Linux -- We call this the "Host".
-- A good quality USB cable.
-- A correct Android Firmware for your target. The Official Chuwi Factory version is currently found here:
http://forum.chuwi.com/thread-1160-1-1.html
(Note that the newest official firmwares are less prominately linked at the bottom, dated 21061008)
-- The Intel® Platform Flash Tool Lite.  Currently version 5.8.2.0 as of this writing.  Get it from:
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
 
Optional, depending on what you want to do:
 
-- The gpt.bin file from post #5 of this thread:
http://forum.chuwi.com/thread-3272-1-1.html
This is needed only if you want to re-size your Android partition so that all of the 64MB internal EMMC is available to Android. This will delete Windows and all Data. This will not leave room for another OS (such as Windows)
Explanation of this file can be found at:
https://forum.xda-developers.com/showpost.php?p=65823981&postcount=144
Thanks to supercowz
 
-- The The "flash-no-erase-all.json" file from the same link as the official firmware -- If, and only if you want to try to keep Windows, although as mentioned, I cannot guarantee that your Windows partition/data will not be wiped even with this file. I have no interest in using Windows, so I did not test this.
http://forum.chuwi.com/thread-1160-1-1.html
 
In other words, you essentially need one of those 2 files, but never both.
 
No USB drivers are needed for Linux, but you may need to ensure you have permissions to the relevant USB device. There are many articles on adding a udev rules for android devices.
 
-- BEGIN
 
Install Intel® Platform Flash Tool Lite. This can easily be done with the Ubuntu Software Center.
 
Unrar the Official Android Firmware.  (Right click and select Extract Here), then extract the zip.  Keep the original rar and zip files.
 
(Optional - Only if you want to attempt to keep a Windows or other OS Partition):
            Extract the flash-no-erase-all.json file from the Hi12.rar
            Copy the flash-no-erase-all.json into the un-zipped firmware folder. Note the existing flash.json in the same location.
 
(Optional - Only if you want to use the full EMMC for Android):
            Extract the gpt.bin file.  Replace the gpt.bin file in the un-zipped firmware folder with this one.
 
Start Intel® Platform Flash Tool Lite.
 
Using the blue "Browse" button near the top, navigate to the Folder Containing the firmware (the un-zipped one). Select the appropriate .json file in that folder. Make sure the correct file is shown next to "Flash File:"
 
Power off the Chuwi Tablet if it not already off.
 
Press and Hold the Vol +, and Vol - buttons, in other words, hold both sides of the volume rocker down.
 
Simultaneously Press and Hold the Power Button until the tablet powers on.  Continue to hold Vol + and Vol -, but you can release the Power button once you see the Chuwi Logo.
 
Continue holding the volume rocker until you see "DNX FASTBOOT MODE.." in small yellow letters near the Chuwi Logo.
 
Connect the USB cable from the host to the Micro USB port on the target.
 
Verify the device shows up in the Intel® Platform Flash Tool.
 
Press the Blue "Start to Flash" button.
 
In a few seconds, the target will reboot in recovery mode.
 
Flashing should take less than 5 minutes.
 
When complete, the tablet will reboot twice.  Do not touch the tablet as it reboots, it may be doing a touchscreen calibration.
 
Disconnect the USB cable.
 
The Chuwi Tablet will boot in Chinese language, and with Chinese apps.
 
To get English or another language:
      Select Settings (the blue/grey gear).
      Select the settings icon that looks like a globe.
      The first item in the globe (Language & input) menu is the language.
 
Erase any unwanted Chinese apps using Settings --> Apps.
 
 
 
Reply Reply Quote Quote Notify of replies Notify of replies  

3  Original Projects and Builds / NodeMCU IoT Clock / Re: NodeMCU IoT Clock Status Update
 on: Feb 1st, 2017, 10:27am 
Started by Administrator | Post by Administrator
2 Status updates:
 
1. My current Source Code (as in the source thread) contains a fairly blatant bug.  When an alarm is playing, the relevant sound file is (obviously) open each time the sound is playing. If the user then requests (or refreshes) the web page, the webserver must open the relevant HTML file. While newer NodeMCU firmwares will allow 2 files to be open at once, the version I used did not.  The result is that there is a very high probability of a crash when attempting to cancel an alarm or hitting snooze. While a crash serves (in a rather un-elegant way) to silence the alarm, and the clock resumes normal function after it reboots, this renders the snooze function unuseable.
 
2. Newer firmwares allow 2 files to be open at the same time, but have another problem. The End User Setup module is being really written, but currently contains bugs that prevent its use.
 
This issue can be fixed by having "handshakes" between the web server and the sound player to avoided having 2 files open at the same time, or wait for a multi file firmware that works, and rewriting the source accordingly.
Reply Reply Quote Quote Notify of replies Notify of replies  

4  Original Projects and Builds / NodeMCU IoT Clock / NodeMCU IoT Clock Source Code
 on: Dec 20th, 2016, 7:27pm 
Started by Administrator | Post by Administrator
Initial release:
 
http://linuxslate.com/files/NodeMCU_IoT_Clock.tar.gz
 
Please see status and bug list here:
http://linuxslate.com/cgi-bin/forum/YaBB.pl?num=1480473161
Reply Reply Quote Quote Notify of replies Notify of replies  

5  Original Projects and Builds / NodeMCU IoT Clock / NodeMCU IoT Clock Status Update
 on: Nov 29th, 2016, 9:32pm 
Started by Administrator | Post by Administrator
My Clock is very near initial release (source code release).
 
UPDATE: Significant Progress
 
Now Working:
 
Both Alarms, Including saving the settings.
 
Saving basic display settings, and restoring them on next boot.
 
More aggressive attempts to contact the SNTP server if a timesync fails. It now will attempt a time sync every minute for 10 minutes if there is a sync fail. This is both on the initial sync, and on hourly syncs. If after 10 tries, there is still no successful sync, it displays a different message, and does not try again until the next regular hourly attempt. In no case have I seen more than 8 consecutive tries fail.
 
New fixes as of 06 Dec:
 
Web pages for Main Settings and both alarms now correctly show current settings when set/viewed, including across a re-boot.
 
Minor bugs related to the above have been fixed:
 
Alarm text was loosing formatting across a re-boot - Fixed.
 
Crash on Alarm if unit had been re-booted/power cycled - Fixed.
 
Error in display of alarm days.  - Fixed.
 
Distribution of the code has been delayed to allow these features to be in the initial release.
 
Initial Code released.
 
I have added basic "Factory Reset" functionality.  Upon selecting Factory Reset from the main page, a confirmation page is displayed. Upon confirming, the settings files are deleted, all settings are set to default, and the Web pages are re-written. The AP is then set to defaults.  This deletes WiFi passwords, and causes End User Setup to run on boot.
 
Other Fixes:
 
I received the red plexiglass, and it looks awesome.  There are still a few light leaks on the top and sides, but "production" units will not have this.
 
The bottom is a clear, but dotted, and much thicker piece of plexiglass. There is some light leakage out the bottom, but with the unit up on little rubber feet (LRF), this light leakage looks really cool, and is not significant enough to interfere with sleep (Opinion, not a medical evaluation), so I am planning to leave it this way in the next one(s) I make.
 

 
I also came up with a really simple solution to the clicking noise -- Install the back panel.  It attenuates the clicking significantly, but the Alarm tones are still more than loud enough.  This is only a solution for the prototype. I still need to order some audio amplifier modules for the "production" units.
 
Not yet fixed:
 
Web pages show default settings, not current/saved settings (except network settings, which works as expected).  Dynamically saving/generating the settings pages will require more code.
Fixed.
 
Setting the 2 alarms within 10 minutes of each other may still cause unpredictable results. (Code not checked/tested for this condition.)
 
Punctuation in the Alarm Messages still causes messages to be displayed "funny" (control character codes are displayed).
 
In addition to the above, more checks for valid inputs (settings) are needed.  Ex: Proper format for Alarm Time.
 
Weather not yet implemented.  Still anticipating possible memory problems when this code is added.
Reply Reply Quote Quote Notify of replies Notify of replies  

6  Mobile Linux Devices / General News / Moved: FU209SCPB-T 1 Line x 20 Character VFD's
 on: Oct 22nd, 2016, 4:51pm 
Started by Administrator | Post by Administrator
This topic has been moved to NodeMCU IoT Clock by Administrator.
Reply Reply Quote Quote Notify of replies Notify of replies  

7  Original Projects and Builds / NodeMCU IoT Clock / FU209SCPB-T 1 Line x 20 Character VFD's
 on: Oct 22nd, 2016, 4:51pm 
Started by Administrator | Post by Administrator

BASIC USE OF FU209SCPB-T
1 Line x 20 Character VFD's
PW-107-100K
PW-283-00
 
Data Provided by John
linuxslate.com
 
Hardware:
 
Power is 5 Volts Regulated (4.75 – 5.25V).  The Unit Draws approximately 0.5 Amps regardless of what is displayed.
 
 _______________________________________________________________
|
|  6  - N.C.                                                JJJJJJJ
|  5  - Rx Serial Data                                      01234CT
|  4  - GND
|  3  - N.C.
|  2  - N.C.
|  1  - +5V
|_______________________________________________________________
 
J0 – The function of this jumper is unknown.
J1 – Is shorted as provided.  The function of this jumper is unknown.
J2-JC – The function of this jumper is unknown.
JT – Is TEST.  Short Prior to power up for Test Mode. In Test Mode, The Character Map is Displayed.
 
Serial Data is 5V TTL Serial Data.  As provided it is run through an inverter glued to the back of the board.  Use this if you are connecting the display directly to an inverted (compliment) TTL serial signal (such as directly to another chip.) If connecting to a serial port or FTDI, this inverter needs to be bypassed. (In other words, the top pin of the larger connector can be connected directly to pin 5 of the left connector)
 
Other Serial Lines are not needed as there is no need for the display to send data back to the host.
 
WARNING: VFD (Vacuum Fluorescent Displays) Operate on HIGH VOLTAGE. There is a step-up circuit that boosts the 5 volts to Several Hundred volts. Touching the Pins Leading to the Glass Tube (or other points) can lead to an Electric Shock even if nothing is displayed.
 
 
Serial Settings:
 
As provided, Set serial port to 1200 N81  - 1200 Baud, No Parity, 8 bits, 1 Stop bit.
 
 
Control Codes:
*** NOTE: UPDATED with scrolling information ****
 
Ctrl – H            Backspace (Non Destructive)            
Ctrl – J            Line Feed  (LF)
Ctrl – M            Carriage Return (CR)
                 *Note: To Clear the display, and begin from the Left again, You must send a CR and a LF, Windows terminals may send CR and LF when you hit [Return]. Linux/Mac [Return] Sends only a CR.
Ctrl – O            Blinking Cursor ON
Ctrl – N            Blinking Cursor OFF  
Ctrl - S (XOFF)   Scrolling ON (Characters at end of line will side-scroll display)*
Ctrl - Q (XON)    Scrolling OFF (Characters at end of line will just overwrite last character)
Ctrl – K            Blink Text ON            
Ctrl – L            Blink Text OFF            
Ctrl – I            Cursor Forward (Tab of 1 space)
 
* Scrolling will happen as fast as characters come in, so speed must be controlled in software.
 
Other Data:
 
The display is run by a M28802M2 8 bit micro controller. As far as I know, this controller is mask programmed for this application, and other code cannot be loaded onto the controller.
 
Connection to FTDI:
 
FTDI                  Display
 
GND      -      -      GND
5V      -      -      5V
TXD      -      -      Serial Rx
 
– Bypass Inverter chip on back of display.
– Other pins not needed.
– Using an FTDI allows the display to be plugged directly into a USB port. Most USB Ports should power the display with no problem.
– There are no Lower Case Characters.
 
 
Application:
 
Super Simple Shell Script to make a Digital Clock (Does not use any LCD or VFD drivers):
 
#!/bin/bash
stty -F /dev/ttyUSB0 1200
while true; do
printf "\r `date +'%a %d %b %H-%M-%S'`"  > /dev/ttyUSB0
sleep 1
printf "\r `date +'%a %d %b %H %M %S'`"  > /dev/ttyUSB0
sleep 1
done
 
 
Super Simple Shell Script to make a System Load Display:
 
#!/bin/bash
stty -F /dev/ttyUSB0 1200
while true; do
printf "\rLOAD`cat /proc/loadavg |cut -c -14` "  > /dev/ttyUSB0
sleep 1
printf "\rLOAD`cat /proc/loadavg |cut -c -14`*"  > /dev/ttyUSB0
sleep 1
done
Reply Reply Quote Quote Notify of replies Notify of replies  

8  Mobile Linux Devices / General News / Using the Wouxun KG-UV9D(plus) Software on Linux
 on: Oct 12th, 2016, 9:07pm 
Started by Administrator | Post by Administrator
I recently purchased a Wouxun KG-UV9D(plus) HT Ham Radio. So far it is a much better radio than the other popular brand of Chinese radio in both features and quality.
 
However, this radio is not supported by CHIRP, the Open Source radio programming software.
http://chirp.danplanet.com/projects/chirp/wiki/Home
 
It is promised to be supported, however development seems to be going more slowly than the Chinese product development cycle, so it is likely that by the time it is supported, I will probably already have a newer radio.
 
At least for the short term, my best hope for being able to program this radio from other than the radio itself is running Wouxun's software under Wine.
 
Fortunately, this does seem like it will work, however, there is another problem. Apparently, the Wouxun KG-UV9D(plus) uses a different cable than the older models or Wouxun radios.
 
According to the CHIRP Cable Guide, Wouxun should use the same cables as Baofeng:
http://chirp.danplanet.com/projects/chirp/wiki/CableGuide
 
However, I made a cable that goes from my FTDI board to my Baofeng UV-5R.  It works fine with CHIRP and the Baofeng, but does not work with the Wouxun KG-UV9D(plus).
 
Note also that many vendors list separate, but identical looking cables for the KG-UV9D(plus) and the other Wouxun radios.
 
If anyone can confirm similar or different cables, and/or provide the pin-out for the KG-UV9D(plus), it would be much appreciated.
 
Other than that, getting the Wouxun KG-UV9D(plus) programming software running under Linux is pretty straight-forward.
 
The following assumes:
  • Recent Linux Distribution, for which a Recent WINE is available and installed.
  • A Wouxun KG-UV9D(plus)
  • An FTDI board that is supported under Linux (most common ones)
  • The correct cable to go from the FTDI to the Radio.

 
Steps:
 
1.  Set up the serial device corresponding to the FTDI. It is assumed the FTDI shows up as /dev/ttyUSB0. This is done one of 2 ways:
1a.  (Temporary) - Give your self permissions to the serial device:
 
sudo chmod 666 /dev/ttyUSB0
 
1b.  (Permanent) - add yourself to the dialout group:
 
sudo usermod -a -G dialout
 
Log out, and log back in again.
 
2.  Link your FTDI (or cable) serial port to a DOS Device:
 
ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com1
 
3.  Use winetricks to install fonts and some needed DLL's:
 
winetricks corefonts
winetricks mfc42
winetricks msvcirt
 
4. Make a symlink to your Wine C: Drive (Optional, but it makes using wine easier)
ln -s /home/john/.wine Wine_C_Drive
 
5. Download the Wouxun KG-UV9D(Plus) software from:
http://www.wouxun.com/resource.aspx
 
6. Extract the Wouxun Programming software:
  - Locate UV9DP_SEN.rar in your Downloads folder (or where ever you downloaded it to).
  - Right click on it, and select "Extract Here"
  - Locate KG-UV9D(Plus) setup.exe in the same folder.
 
7. Run the Windows Installer.  This should work by just double clicking KG-UV9D(Plus) setup.exe, if wine and the wine program loader is installed properly.
 
8.  Navigate to the installed Windows Application
 -- Double click the link you created in step 4.
 -- You should see a KG-UV9D(Plus) directory inside either the Program Files or Program Files (x86) Folders.
 -- Double click KG-UV9D(Plus).exe to launch the Wouxun application.
 
Troubleshooting
 
If it does not work, try running KG-UV9D(Plus).exe from the command line.  For example:
wine .wine/drive_c/Program\ Files\ \(x86\)/KG-UV9D\(Plus\)/KG-UV9D\(Plus\).exe
(Note escapes on the "()" characters.)
Note any error messages.  If they indicate a missing DLL, try installing it using winetricks as we did in step 3.
 
If you are missing text (fonts) execute it from within the directory -- e.g.:
cd ~/.wine/drive_c$ cd Program\ Files\ \(x86\)/KG-UV9D\(Plus\)/
wine KG-UV9D\(Plus\)
 
Reply Reply Quote Quote Notify of replies Notify of replies  

9  Mobile Linux Devices / Z1/Rock/Vega Android 2.2 GSM Watch Phone / Yet another MTK6572 Android Watch - Android 4.2
 on: Jul 25th, 2014, 7:50pm 
Started by Administrator | Post by Administrator
inWatch z Android 4.2 Dual-core Watch Phone
 
http://www.dx.com/p/inwatch-z-android-4-2-dual-core-watch-phone-w-1-63-screen-wi -fi-gps-ram-1gb-rom-8gb-black-334287
 
Android 4.2  (Claimed - No screen shots of settings or benchmark apps to prove it.)
MTK6572 Dual-Core
2G Only
Claims it will work as a bluetooth accessory, or a stand-alone phone.
Google Play (again, no screen shot showing this.)
Sapphire "table cover"(?!) + stainless steel shell, ceramic back cover
 
Camera faces the same way as Z1
 
 
 
Reply Reply Quote Quote Notify of replies Notify of replies  

10  Mobile Linux Devices / Other Android Mobile Phones and Tablets / Phonebaby v5
 on: Jun 20th, 2014, 9:14pm 
Started by Tim | Post by Tim
I have this small phone running android 4.0.4.
http://www.aliexpress.com/item/2013Hot-sale-Mini-phone-Phonebaby-i5s-Android4-0- MTK6517-Dual-Core-Multi-touch-RAM256MB-ROM-256MB/1455440852.html
 
specs
4.0.4
 
kernel
 3.0.13
 
build number
ALPSICS2.MP.V1.27
 
Custom build version
1380350960
 
Question would it be possible to make a recovery to use with rom manager and also put a custom rom on it.
Thanks for any answers.
Reply Reply Quote Quote Notify of replies Notify of replies