Related
kaiser ubuntu port based on zubuntu by Omegamoon for Sharp Zaurus was successfully launched on HTC Nike!
Instructions:
1. download kernel
http://84.23.71.227/kerneloftheday/zImageUbuntu
2. download ubuntu basefiles and rootfs
3. place ubuntu.img, haret, initrd.gz and zImageUbuntu to Storage Card/ubuntu/
4. place this default.txt there too
Code:
set RAMADDR 0x10000000
set MTYPE 1724
set KERNEL zImageUbuntu
set initrd initrd.gz
set cmdline "pm.sleep_mode=1 mddi.width=320 mddi.height=480 lcd.density=160 board-htcnike-keypad.keypadlayout=1 board-htcnike-keypad.sticky_timer_time_ms=350 no_console_suspend"
boot
5. change board-htcnike-keypad.keypadlayout=1 to 0 if you have 20key nike.
6. run haret and press "Run", ubuntu & kernel will be loaded to login prompt, login with username root and no password, you will get root shell.
7. write
Code:
export TSLIB_TSDEVICE=/dev/input/event0
ts_calibrate
and calibrate your screen.
8. write startx and see LXDE running on your nike! you've got real linux box in pocket!
Note, rootfs for ubuntu needs 1GB of free space on your sdcard!
For now, you cannot work with screen, we have some difference from kaiser panel's, i.e. ubuntu gui is completely unusable, this thread were started to find out why.
based on this thread from kaiser forum.
Credits: dzo, Omegamoon, domy007, mblaster and guys from Rhodubuntu thread.
I dont get any response when i try to calibrate screen on niki 200
thats strange, it must work.
I will debug on touchscreen problems, but ubuntu running and that is great, now we have only input-devices problems, and this is more better than nothing.
Sounds great, but wouldn't it be better to try something smaller like puppylinux or Feather linux ?
zubuntu is only we have compiled for ARM and working with our hardware that starts X and tested on other htc's devices.
rzk333 said:
zubuntu is only we have compiled for ARM and working with our hardware that starts X and tested on other htc's devices.
Click to expand...
Click to collapse
Ok thanks for the information, did some reading before and was always wondering why they use ubuntu but this answer set things straight.
Greetz,
Great to see a full linux distro around for htc devices. I will fix the '_' tomorrow... Any other missing characters?
How is the speed of ubuntu? Is it very sluggish or usable?
'=' character maybe, for export line.
zImageUbuntu is updated (your link is still valid).
'=' and '-'are on '*'-button, '_' is Alt-
I have included the msm_fb_refresh and the keypad changes into my auto-updated-kernel, so you should be able to use the fresh kernels from my thread with ubuntu if you want recent updates (zImageUbuntu is not automatically updated).
got some progress,
1) msm refresh thread seems to disable sleep mode in android, thread polls framebuffer many times in second and drains battery.
2) linux logo on bootup must be disabled - logo gets over ts_calibrate's first crosshair point.
2) still trying to make touchscreen and tslib friends - i2c bus debug messages logs saying that touchscreen is connected and recieves data correctly.
found some data:
/dev/input/event0 - htcnike-kbd
/dev/input/event1 - htcnike-ts
but still no data from touchscreen...
rzk333 said:
got some progress,
1) msm refresh thread seems to disable sleep mode in android, thread polls framebuffer many times in second and drains battery.
2) linux logo on bootup must be disabled - logo gets over ts_calibrate's first crosshair point.
2) still trying to make touchscreen and tslib friends - i2c bus debug messages logs saying that touchscreen is connected and recieves data correctly.
found some data:
/dev/input/event0 - htcnike-kbd
/dev/input/event1 - htcnike-ts
but still no data from touchscreen...
Click to expand...
Click to collapse
Disabled msm refresh thread from the android kernels again. The kernel you linked in your first post is now automatically updated with anything new in the repository. Bootlogo is disabled, too. Good luck with tslib, let me know if when you need something else to be hacked into the kernel.
mblaster
I've just test the usb ether function in the zImage from the post
showthread.php?p=6675397
and it works just fine.
(Just when I had managed to make adbd works... but ssh is more reliable)
Thanks gTan64.
wow, that is good, now I can dump system state without hours of keyboard typing
I've managed to get internet by usb (cdc only) thanks to gTan64: just apply the patch from is post ("Debian on the vogue"), you can extract it from the download links.
And the TOUCHSCREEN WORK!!!!!!!
But you need to compile tslib from the tslib git (github.com/kergoth/tslib.git), the one in the rootfs from this post doesn't work.
Will make a more complete post later, I think.
Bye.
Ubuntu always shows me a black screen when I try to startup it!
What can I do make it work?
omg, I knew that something is wrong with tslib in this rootfs!
thanks for r&d, if you will make some packages & mans, I'll add them to first post.
Maybe you can upload some pics ?
But you need to compile tslib from the tslib git
Click to expand...
Click to collapse
I tried to compile - but no luck, autoconf fails to make configure...
I also uploaded debian rootfs and posted links in gTan's Debian on Vogue thread.
nothing happened last month?
ATM7013,gs701b,gl5201 -- with gsl1680 touch processor.(i open it),polaroid rainbow 7" multitouch, midc407 pr005,
After i flash-it with 'action tablet tool product' (icecream_gs701b_q8_rgb.fw,acta.img,actab.img) ,touch doesn't work anymore.
i can root it.i can use MOUSE with OTG adaptor
i try to install another touch driver : insmod---gsl1680.ko and i get (exec format error),isnmod---glsX680-tp.ko is ok,but my touch don't work.
gslX680-tp.ko is in my /system/lib/modules already and i have also /system/usr/idc/gslX680-touch.idc(i try to modify gslX680-touch.idc to gslX680-tp.idc and nothing happen.
in lsmod i get gslX680_touch 0 - Live
getevent
add device 1: /dev/input/event0
name: "gslx680"
i try to flash anothers firmware but is the only one who work,i try 30 firmware,mips.
if i try to flash UPGRADE_FAST.fw , i get black scree and nothing work,even ADFU is not work anymore,i need to press pin 7 and pin 8 from NAND flash,to come in ADFU mode.
so...with linux driver i can extract misc.img and system.img and the flash with Action Tablet Tool Product.
Also i can modify easy misc.img in WinImage for windows.but i can't modify system.img,only i can explore it with ext2explorer.
AND i try maaaany firmwares from TF card.i format it FAT32 and copy inside firmware like...update.zip (don't work),UPGRADE_FAST.fw(don't work)
If someone have the same tablet,and if he want to give me the firmware.
or if someone want to help me
Thanks
EDIT:if is multi-touch i need to install more touch drivers ?like----
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ????
to have in lsmod ---- ft5x_ts 7 - LIVE goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ??
and touch drivers for JB 4.2.2 work also for ICS 4.0.3 ?
polaroid midc704
blad3_sv said:
ATM7013,gs701b,gl5201 -- with gsl1680 touch processor.(i open it),polaroid rainbow 7" multitouch, midc407 pr005,
After i flash-it with 'action tablet tool product' (icecream_gs701b_q8_rgb.fw,acta.img,actab.img) ,touch doesn't work anymore.
i can root it.i can use MOUSE with OTG adaptor
i try to install another touch driver : insmod---gsl1680.ko and i get (exec format error),isnmod---glsX680-tp.ko is ok,but my touch don't work.
gslX680-tp.ko is in my /system/lib/modules already and i have also /system/usr/idc/gslX680-touch.idc(i try to modify gslX680-touch.idc to gslX680-tp.idc and nothing happen.
in lsmod i get gslX680_touch 0 - Live
getevent
add device 1: /dev/input/event0
name: "gslx680"
i try to flash anothers firmware but is the only one who work,i try 30 firmware,mips.
if i try to flash UPGRADE_FAST.fw , i get black scree and nothing work,even ADFU is not work anymore,i need to press pin 7 and pin 8 from NAND flash,to come in ADFU mode.
so...with linux driver i can extract misc.img and system.img and the flash with Action Tablet Tool Product.
Also i can modify easy misc.img in WinImage for windows.but i can't modify system.img,only i can explore it with ext2explorer.
AND i try maaaany firmwares from TF card.i format it FAT32 and copy inside firmware like...update.zip (don't work),UPGRADE_FAST.fw(don't work)
If someone have the same tablet,and if he want to give me the firmware.
or if someone want to help me
Thanks
EDIT:if is multi-touch i need to install more touch drivers ?like----
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ????
to have in lsmod ---- ft5x_ts 7 - LIVE goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x ??
and touch drivers for JB 4.2.2 work also for ICS 4.0.3 ?
Click to expand...
Click to collapse
nobody? realy? not any advice ?
I am trying to set up an Android Virtual Device (AVD) running Android L Preview so that I can begin developing an app using the new Material Design theme. I already have AVDs set up running KitKat and Gingerbread, it is only the Android L Preview that is not working. I have tried both the AVD Manager built-in to Android Studio, as well as from a separate installation of the Android SDK.
Here is my config.ini:
Code:
avd.ini.encoding=ISO-8859-1
abi.type=armeabi-v7a
disk.dataPartition.size=1024M
hw.accelerometer=yes
hw.audioInput=yes
hw.battery=yes
hw.camera.back=webcam0
hw.camera.front=emulated
hw.cpu.arch=arm
hw.cpu.model=cortex-a8
hw.dPad=no
hw.device.hash2=MD5:2fa0e16c8cceb7d385183284107c0c88
hw.device.manufacturer=Google
hw.device.name=Nexus 5
hw.gps=yes
hw.keyboard=yes
hw.lcd.density=480
hw.mainKeys=no
hw.ramSize=2048
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images\android-L\default\armeabi-v7a\
sdcard.size=1024M
skin.dynamic=no
skin.name=1080x1920
skin.path=1080x1920
tag.display=Default
tag.id=default
vm.heapSize=64
When I start the AVD I just get a black screen. I ended up letting it run for 5 hours and it never booted. Looking through the logcat, the following errors are repeated continuously:
Code:
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/default/accept_ra_rt_table: No such file or directory
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/eth0/accept_ra_rt_table: No such file or directory
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/lo/accept_ra_rt_table: No such file or directory
06-27 13:32:31.945 319-319/? E/Netd﹕ Failed to open /proc/sys/net/ipv6/conf/sit0/accept_ra_rt_table: No such file or directory
06-27 13:32:32.293 320-320/? E/SurfaceFlinger﹕ hwcomposer module not found
06-27 13:32:32.293 320-320/? E/SurfaceFlinger﹕ ERROR: failed to open framebuffer (No such file or directory), aborting
06-27 13:32:32.295 320-320/? A/libc﹕ Fatal signal 6 (SIGABRT), code -6 in tid 320 (surfaceflinger)
Here's the full logcat: http://pastebin.com/Ctjy5YLF
Does anyone have any idea what I did wrong or why the emulator isn't working? How can I get this up and running?
Thanks!
Same here
I'm having the exact same issue but not getting any errors in the LogCat. Hopefully someone has a solution. I've downloaded the new Android Studio and tried it but it didn't work. I also re-downloaded the ADT Eclipse bundle and tried it with that. Still no joy.
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Black screen with the emulator running android L
same problem here.. tried host GPU and no luck...
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
Can confirm enabling 'Use Host GPU' has made the emulator work.
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
Now I feel like an idiot. I initially had that selected for my Gingerbread AVD but it displayed an error when starting and disabled the message. I assumed my GPU wasn't compatible for whatever reason so I never tried it with the Android L AVD. Or perhaps it had something to do with trying it over an RDP remote desktop session before. Or my RAMDISK being full. Anyways, it's working now, so thank you.
GPU + Atom x86 has made the emulator go from a black screen to the android startup screen. And now, we wait
Edit: To be clear, I tried GPU + ARM, didn't work.
Edit2: It work, still slow as hell though
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
That worked for me. Thanks a million. :good:
eddieringle said:
I had the same black screen until I enabled "Use Host GPU" under Emulation Options when creating the AVD.
Click to expand...
Click to collapse
This does work for me on Linux
Just an update - I discovered two things.
1 - this was not an issue with the L Preview, but rather with emulating a Nexus 5.
2 - there are two ways to solve the issue, one way is to use host GPU, the other is to select a skin rather than choosing no skin. The nice thing about the second method is that the snapshot feature can be used, greatly increasing the emulator start time.
FWIW.. I noticed..
So apparently the x86 version of Lollipop in the emulator requires the GPU or else you get a blank screen and missing hwcomposer module support files.. (I don't know if the files are in the preview .imgs but haven't gone looking).
If you create an arm (SLOW AS MOLASSES) arm image.. after the forever of booting you can do actual screenshots. It's 32-bit and the colors band, but there ya go.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- you tell me
G9 Play - Ilitek (Work)
G9 Play - Himax (Dead)
G9 Play - Goodix, Chipone (untested)
G9 Power - Novatek (Work)
G9 Power - Focaltech (Untested)
E7 Plus - goodix,himax,chipone (Untested)
Install guide (Might not work):
To flash:
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Download:
GUAMP: MEGA
CEBU: MEGA
GUAM: soon
Reccomended ADB and Fastboot binaries:
platform-tools
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/100Daisy/android_device_motorola_guamp
Kernel source: prebuilt (for now)
Join our device chat in Telegram !
no link xda will remove anyways
gitdaisy applause circle:
https://t.me/GitDaisyShitposting
Donations:
paypal.me/100Daisy
Credits:
I want to say a big thanks to the testers @borraz
Hi! not work touchscreen in HImax.
condor323 said:
Hi! not work touchscreen in HImax.
Click to expand...
Click to collapse
contact me on Telegram @GitDaisy
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
jarchig said:
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
Click to expand...
Click to collapse
I will cover that issue in next release, then i will focus on bringing one image for all bengal devices released with A10 (G30 has vendor_boot and dt seems to not be compatible and kernel may be not compatible too)
currently i need to ship different prebuilts for all devices
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
@Mauricio Oliveira , you have the correct smartphone model (guamp). It is the same as mine.
However, there are several touchscreen variants and your application (cpu-z) does not show which variant you have.
Can you install the 'Device Info HW' application? Your touchscreen will show in the 'General' tab.
Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
Another way to find out your touchscreen manufacturer is by connecting to your mobile using the ‘adb shell’ command.
From your desktop, run:
Code:
adb shell
and then
Code:
getevent
the command will show output like the following:
Code:
guamp:/ # getevent
add device 1: /dev/input/event2
name: "chipone-tddi"
add device 2: /dev/input/event0
name: "qpnp_pon"
add device 3: /dev/input/event1
name: "gpio-keys"
In this case, ‘chipone-tddi’ is the touchscreen manufacturer.
ok, obrigado pelo feedback .
Hello everyone on the forum... Thanks again my friend jarchig. I noticed that my screen variant is the same as yours... Read in your posts that you have successfully added commands to enable it. Could you teach step by step how to do this?
Thank you in advance.
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
did twrp work for anyone?
piperoman said:
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
Click to expand...
Click to collapse
I see that nobody respond to you...
I use the image from the link that you share, specifically RETLA. You must download the zip file, decompress it and you can see the vbmeta.img file
GitDaisy said:
contact me on Telegram @GitDaisy
Click to expand...
Click to collapse
it doesn't work for me too, the himax touchscreen ,guamp version, can you help me?
If the android version is 11 how does it work? mine has android 11 sorry i think there is no solution for me
Hello everyone,
I'm attempting to manipulate the gyro values on my Android device that's currently running LineageOS 18.1. After verifying the device, I had assumed there would be specific files in the /dev/input directory where I could send the desired value to. Upon executing the command "getevent -l", I received the following output:
```
add device 1: /dev/input/event8
name: "uinput-fpc"
add device 2: /dev/input/event7
name: "sdm660-snd-card Button Jack"
add device 3: /dev/input/event6
name: "sdm660-snd-card Headset Jack"
add device 4: /dev/input/event3
name: "uinput-goodix"
add device 5: /dev/input/event1
name: "ant_check-input"
add device 6: /dev/input/event2
name: "synaptics_dsx"
add device 7: /dev/input/event5
name: "gpio-keys"
add device 8: /dev/input/event4
name: "hall-switch-input"
add device 9: /dev/input/event0
name: "qpnp_pon"
```
Unfortunately, none of these inputs appear to be connected to the gyro. However, I did manage to uncover the name of the gyro, which is BMI120. Despite this, I was unable to locate anything relevant in the kernel : https://github.dev/LineageOS/android_kernel_xiaomi_sdm660
If anyone could point me in the right direction on how to make these changes, I would greatly appreciate it.
Thank you.