Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - spa

Pages: [1] 2
Cosmo Communicator - Android / Re: need to reflash stock android image
« on: April 27, 2021, 11:54:57 pm »
There is this on the Planet website which supports the manual installation of Cosmo Android V19, V22 and V23 complete with download files.

It is image for multi-boot . It is not complete for system restore.

With V19, you can use Custom TWRP to backup and restore only the DATA partition(Internal storage). So, I use V19 for this purpose.

Cosmo Communicator - General Discussion / Re: Hard keyboard launcher
« on: January 14, 2021, 02:40:52 am »
Added text input function to key launcher (requires rooted)

See the video below for key features.
1.Original feature
2.Key launcher "Multi mode"
3. Key launcher "Not Multi mode"

My Gemini's battery died, so I haven't tested it on Gemini.

Cosmo Communicator - General Discussion / Re: Camera
« on: January 04, 2021, 09:12:25 am »

Cosmo Communicator - General Discussion / Re: Camera
« on: January 04, 2021, 01:06:25 am »
The "camera sounds" setting that existed in v3 is no longer available in v4.
I will wish the "camera sounds" setting was still there.

Astro Slide - Hardware / Key size
« on: January 03, 2021, 09:55:57 pm »
I saw Astro's keyboard photo in Update #15.
I was very disappointed.
The width of the up/down keys, left shift, and left CTRL key is different from the other keys.
It makes it impossible to swap the location of these keys with other keys.
I used to use Gemini and Cosmo by swapping the keys.
The ability to freely swap keys was one of the great things about Gemini and Cosmo.
There is no advantage to changing the width of the keys.
I requested Planet to make Astro the same as Gemini and Cosmo.

Cosmo Communicator - General Discussion / Re: Camera
« on: December 31, 2020, 09:16:20 pm »
Very thanks, and happy new year.

Cosmo Communicator - Android / Re: need to reflash stock android image
« on: December 17, 2020, 08:44:00 pm »
I am Japanese. This document has been prepared using automatic translation.
This is the result of reverting from V22 to v19.
There are no results for recovery from V23.
Cosmo will be initialized.
I am not responsible for the result of the work.

What you need
A micro SD card with at least 5GB of free space
A PC with ADB connection
TWRP uses the following. I am not using TWRP provided by Planet.

Another note
TWRP can only backup and restore the Data partition under v19.
If you restore other partitions, Cosmo Communicator do not boot.

Download the file.
MD5 digest c14905bf510744f42e6194eaeeddf773

Unzip the downloaded file.
Create the \v19 folder on the Micro SD.
Store the 29 unziped files in the v19 folder. Be careful not to encrypt EFS.
Insert the micro SD into Cosmo.

Start TWRP.
Select "Mount" from the TWRP menu
please mount "storage1"
Run adb shell from your PC and check the following
- The prompt is # (which means rooted)
- There are 29 files under /auto0-1/v19.

Overwrite partitions with the v19 images.
Execute Command line by line from the adb shell.

dd if=/auto0-1/v19/boot.img of=/dev/block/mmcblk0p30 bs=4096
dd if=/auto0-1/v19/cam_vpu1.img of=/dev/block/mmcblk0p22 bs=4096
dd if=/auto0-1/v19/cam_vpu2.img of=/dev/block/mmcblk0p23 bs=4096
dd if=/auto0-1/v19/cam_vpu3.img of=/dev/block/mmcblk0p24 bs=4096
dd if=/auto0-1/v19/dtbo.img of=/dev/block/mmcblk0p32 bs=4096
dd if=/auto0-1/v19/expdb.img of=/dev/block/mmcblk0p4 bs=4096
dd if=/auto0-1/v19/frp.img of=/dev/block/mmcblk0p5 bs=4096
dd if=/auto0-1/v19/lk.img of=/dev/block/mmcblk0p28 bs=4096
dd if=/auto0-1/v19/lk2.img of=/dev/block/mmcblk0p29 bs=4096
dd if=/auto0-1/v19/md1dsp.img of=/dev/block/mmcblk0p16 bs=4096
dd if=/auto0-1/v19/md1img.img of=/dev/block/mmcblk0p15 bs=4096
dd if=/auto0-1/v19/metadata.img of=/dev/block/mmcblk0p8 bs=4096
dd if=/auto0-1/v19/nvcfg.img of=/dev/block/mmcblk0p6 bs=4096
dd if=/auto0-1/v19/nvdata.img of=/dev/block/mmcblk0p7 bs=4096
dd if=/auto0-1/v19/para.img of=/dev/block/mmcblk0p3 bs=4096
dd if=/auto0-1/v19/persist.img of=/dev/block/mmcblk0p12 bs=4096
dd if=/auto0-1/v19/protect1.img of=/dev/block/mmcblk0p9 bs=4096
dd if=/auto0-1/v19/protect2.img of=/dev/block/mmcblk0p10 bs=4096
dd if=/auto0-1/v19/recovery.img of=/dev/block/mmcblk0p2 bs=4096
dd if=/auto0-1/v19/scp1.img of=/dev/block/mmcblk0p18 bs=4096
dd if=/auto0-1/v19/scp2.img of=/dev/block/mmcblk0p19 bs=4096
dd if=/auto0-1/v19/seccfg.img of=/dev/block/mmcblk0p11 bs=4096
dd if=/auto0-1/v19/spmfw.img of=/dev/block/mmcblk0p17 bs=4096
dd if=/auto0-1/v19/sspm_1.img of=/dev/block/mmcblk0p20 bs=4096
dd if=/auto0-1/v19/sspm_2.img of=/dev/block/mmcblk0p21 bs=4096
dd if=/auto0-1/v19/system.img of=/dev/block/mmcblk0p36 bs=4096
dd if=/auto0-1/v19/tee1.img of=/dev/block/mmcblk0p33 bs=4096
dd if=/auto0-1/v19/tee2.img of=/dev/block/mmcblk0p34 bs=4096
dd if=/auto0-1/v19/vendor.img of=/dev/block/mmcblk0p35 bs=4096

Finally, Sync.

Reboot Cosmo Communicator.
It will take longer than usual; it should boot within 3 minutes.
"Decryption unsuccessful" will be displayed; select "RESET PHONE".
You may be asked for the screen lock password that you had set.
The system will initialize and boot normally.

Clear Cashe.
Please reboot.
Select "RECOVERY boot"
ESC + VOLUP(behind the screen)
Select "Wipe cashe partition"

Cosmo Communicator - Android / Re: need to reflash stock android image
« on: December 17, 2020, 09:44:07 am »
You may be able to recover it with the procedure I used to revert to V22->V19. I will describe the procedure in a few days. I suggest you do not do any more extra work.

Cosmo Communicator - Hardware / Re: Rubber feet peeling off
« on: November 04, 2020, 06:50:10 pm »
If you zoom in with a loupe, you can see the structure.
Pull it and then push it back in.

i get that behavior even for normal calls...  maybe you are lucky. ::)

Is it about ringtone or vibration?
My Cosmo Communicator ringtone are normal. The vibration does not continue.
As for the vibration, CosmoCtl will fix it.

Cosmo Communicator - General Discussion / Re: Hard keyboard launcher
« on: October 29, 2020, 09:47:40 pm »
Sorry, It is not open source.

Cosmo Communicator - General Discussion / Hard keyboard launcher
« on: October 28, 2020, 10:46:16 pm »
I made a keyboard launcher. I hope you'll give it a try.
It is not a home app. It is no need to change the current home app.
It has been tested on Cosmo Communicator, GeminiPDA and F(x)tec Pro1.

Q When I press a key on the home screen, Google starts up.
A Set a Modifier key or disable Google App.

Q Other apps are displayed in the background of the startup screen.
A Open the setting screen and tap "Back" to return to the initial setting screen and then close, or reboot.

Q Accessibility service is not "running".
A. Reboot.

Q It sometimes takes a long time to display the startup screen after I press the key.
A It is android specs.
 Please set in "Settings of HOME App" and "HOME settings for OS".
Settings of HOME App
 Delay time until launch. 200ms
 Select HOME. Select the HOME application you are using.
HOME settings for OS.
 Select Multilauncher.

Cosmo Communicator - General Discussion / Re: Camera
« on: October 28, 2020, 10:39:23 pm »
The focus is on the tapped position, but the blinking after tapping occurs at a position shifted by 90 degrees. It is v19. There is no problem in practical use.

Cosmo Communicator - Android / Re: CosmoCtl - howto set it up?
« on: August 04, 2020, 09:12:33 pm »
AutoActivation of keyboard backlight. Nothing changed.

If it doesn't work at all.
Is it possible to change it by Fn+Shift+B, N?
Have you changed your keymap?
CosmoCtl emulates the same key event.

If sometimes it works.
Cosmo's illuminance sensor goes to 0 illuminance at a dimly lit level.
Key light comes on at a dimly lit level.
The Cosmo's illuminance sensor is located on the back.
It may not match the brightness you feel.

Please describe the content of the XML.

Pages: [1] 2