Hi, guys.
You can see that they are porting Android OS for others device using HaRET. I want that it will be for our devices too.
I read about HaRET and tried run HaRET with haretconsole on my device. But I found out that HaRET don't support our device yet. If you have HaRET source code, open file mach-types.h under folder include, you can see there many supported device but not Iolite or open the page
I sent an email to ask about support but nothing isn't now. If someone know how to do please tell me what i have to do?
Hope that Android OS will be ported for our device in the recent day.
Best regard!
woooow let's hope...
HaRET works on my Iolite. But I' a new user and not allowed to post links.
1u21 said:
HaRET works on my Iolite. But I' a new user and not allowed to post links.
Click to expand...
Click to collapse
How do it work?
Yeah, it run but we can't deploy device with it. For example when you run command watch GPIOS (through haretconsole), nothing will be appear
It works, but not really stable. Sometimes ist freezes and some functions don't work like bluetooth. You can send and receive SMS, make some phone calls and go online via WLAN. I don't know, if UMTS is running.
I'm still waiting for a Mod to unlock my account.
But it uses a huge amount of energy.
1u21 said:
It works, but not really stable. Sometimes ist freezes and some functions don't work like bluetooth. You can send and receive SMS, make some phone calls and go online via WLAN. I don't know, if UMTS is running.
I'm still waiting for a Mod to unlock my account.
But it uses a huge amount of energy.
Click to expand...
Click to collapse
Can you send me link via email [email protected], please?
Thanks in advance.
It could be this - kandroid dot org
No. I'm using not the korean version.
Android 2.0 is running on the Iolite, but too unstable. You can't use is it in anyway.
Did you have try it ?
Yes. It fills the whole 256 data.img with software. But the bigger problem is the necessary of a fast CPU. Everything runs slow and is more unstable. The Tattoo is not a similar phone to the Iolite.
I just found my problem. You should use HaRET version 0.5.1 (newest version is 0.5.2).
But I still can't make Android boot. Some changes in zImage are needed?
Android started with an unmodified zImage on my Iolite. But I have some new problems with Android and no time for solving.
Maybe the CPU is to slow for Android.
Can we have a link for the file?
dancer_69 said:
Can we have a link for the file?
Click to expand...
Click to collapse
Here is all versions of HaRET
http://www.handhelds.org/~koconnor/haret/
Click to expand...
Click to collapse
Sorry, I mean a link for android image, and the parameters of default.txt to be able to boot it with haret.
I already know where to find haret
I need it too, please, can you post the link?
Here is it:
http://www.androidonhtc.com/polaris/install
Well, we still need the contents of the "Default.txt" to boot the android image....
Use the normal default.txt and make some changes. Here is my default.txt
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1723
set KERNEL zImage3
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Hitachi 2=Topoly 3=Samsung
# mddi_client_vogue.vsync - Use hardware vsync, default is 1 but should be 0 if
# panel_type is 0
#
set cmdline "board-htckaiser.panel_type=2 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 lcd.density=120 no_console_suspend clock-7x00.mddi=0xa51 clock-7x00.ahb_div=2 clock-7x00.slow=1 clock-7x00.voltage=1 "
boot
Click to expand...
Click to collapse
I'm also using the new version of Android, which you can find on the same page. It works better, but you can feel the difference between 400Mhz and 528Mhz.
Related
If you are familiar with Android already, but are not satisfied with the speed of your system, you might want to try a smaller release, without senseui, etc.
In this case, I recommend you to go to the Google Code: Android for Vogue website.
On this site, you will always find the latest kernels, rootfs's, etc..
The file list of a working Android (on the root of your formatted card):
default.txt
haret.exe
initrd.gz
rootfs.img
system.img
zImage
The default.txt of your Android on a Nike should look like this:
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1724
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htckaiser.panel_type=1 ppp.apn=wnw ppp.username= ppp.password= board-kaiser-battery.battery_capacity=1800 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=20000000 pm.sleep_mode=1 no_console_suspend board-kaiser-keypad.atttilt=1 board-htcnike-keypad.keypadlayout=1"
boot
With these settings, you have keyboard working, power button ends the call, start button is Home, camera button is menu.
Feel free to combine the files, test zImage's, system.img's.
Remember, for a clean start, the only files that should be on the card are listed above. If you leave the previous data.img created at the first start of Android when trying out a new kernel, or system.img, there can be issues, maybe system fail.
Regards, Hope i could help some.
Questions are welcome, i may make a FAQ from them.
Simple, short...
Thank you
Is it possible to get my windows mobile contacts working on android?
Good question, I have the same...
I think it possible through Outlook, exporting to Gmail, but I didn't try this...
Another question; you speak about "board-htckaiser[...]" and the wiki speak about "board-htcnike[...]" is the same options for the two commands ? I'have tested board-htcnike-keypad.keypadlayout=2 for my AZERTY 20keys nike and it work fine...
wm contacts
Yep, you have to copy your contacts to the SIM card, and then in Android, you can access, and copy them to the local storage, and you can also sync them with your Google account, and also, you can link your contacts with Facebook or Twitter users. It will display their picture, news, and birthdays automatically.
Big Up
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?
First this is a patch and not a fix for real mac address.
I have added new cmdline parameter 'wifi.mac_address' which enables you to set any mac address of the wifi interface. So to set a different mac address you need to add new parameter to your startup.txt:
Code:
[STRIKE]set cmdline "wifi.mac_address=00:11:22:33:44:55"[/STRIKE]
I have attached zip file with new zImage and wifi modules for testing purposes. Kernel is based on hastarin sources from Mon Oct 18 17:30:15 2010.
Backup your settings before you test the new zimage and modules.
To discover your mac address in windows look in the following thread:
h__p://forum.xda-developers.com/showthread.php?t=587705&highlight=mac+address
UPDATE: I have made a new patch for the same problem (new files attached). New kernel is based on hastarin sources from Tue Oct 26 22:18:43 2010.
Thanks to clio94 for showing me anther way to change mac address.
UPDATE2: Thanks to OSM for sharing his code for changing bluetooth mac address i have made new patch (and zImage for testing). I have added new parameter "bt.mac" for changing the bt mac address and renamed parameter for changing wifi mac address to "wif.mac" (because is simpler and parameter with the same name is used in michyprima r11 kernel). So for changing the mac address of wifi and bt cmdline looks like this:
Code:
set cmdline "bt.mac=00:11:22:33:44:55 wifi.mac=00:12:23:34:45:56"
If you are using desire HD builds and the patch it's not working you can try method described in:
http://forum.xda-developers.com/showpost.php?p=9806811&postcount=17
mdebeljuh said:
First this is a patch and not a fix for real mac address.
I have added new cmdline parameter 'wifi.mac_address' which enables you to set any mac address of the wifi interface. So to set a different mac address you need to add new parameter to your startup.txt:
Code:
set cmdline "wifi.mac_address=00:11:22:33:44:55"
I have attached zip file with new zImage and wifi modules for testing purposes. Kernel is based on hastarin sources from Mon Oct 18 17:30:15 2010.
Backup your settings before you test the new zimage and modules.
To discover your mac address in windows look in the following thread:
h__p://forum.xda-developers.com/showthread.php?t=587705&highlight=mac+address
Click to expand...
Click to collapse
Nice one, I hope they merge this into the master.
Thanks!
Until they get the NAND code working to read the real MAC address this will do nicely. I'll add it to my next kernel.
Virtual Dynamic MAC Address
this is awesome , i love it .
Virtual Dynamic MAC Address , this is exactly what i was looking for
greaaaaaaaaaaaaaaaaaat job
Long time waiting this feature.
Now hastarin r7.7 also add this feature.
Do you know michyprima R11 used "wifi.mac"
now hastarin r7.7 use "wifi.mac_address"
differenent property name.
Simply awsome !!!!! Been waiting for a fix for the mac issue
setting up
thanks very much. it solved a big problem.
Great job
Help
Ho do you patch the 'patch file' within the zip file?
Thank you in advance.
You need to have kernel sources.You copy the patch in to kernel folder and you give
patch -p1 < /path_to_patch/0001-Patch-for-wifi-mac-address-and-bt-mac-address.patch
Thanks. This is now included in my r8 kernel.
In desire hd build works only the first patch with "wifi.mac_address=00:11:22:33:44:55"
Τhe second version for some reason cannot change the wifi mac address.
Good tip
I have spend hours to understand why i could not connect anymore on my wifi supplier and the solution was just there I put my original winmo mac on the command line and it connects. Thanks a lot.
Thanks a lot for this patch, I have been using it in kernels that it is compiled with. I am going to learn to compile my own kernel soon and will be using it
Just a quick note that for some reason this isn't working in the build I'm now using.
I see that it gets executed but the driver doesn't use it:
Code:
<5>[ 0.000000] Kernel command line: rel_path=desire_hd2 nand_boot=0 wifi.mac=00:23:76:AF:B4:7F
<4>[ 0.000000] htcleo_macaddress_setup: cmdline mac config=00:23:76:AF:B4:7F | arch/arm/mach-msm/board-htcleo-wifi-nvs.c
<4>[ 0.000000] htcleo_macaddress_setup parsed macaddr=macaddr=00:23:76:AF:B4:7F
<4>[ 0.000000] | arch/arm/mach-msm/board-htcleo-wifi-nvs.c
<4>[ 0.000000] htcleo_macaddress_setup parsed mac_address= 0:23:76:af:b4:7f | arch/arm/mach-msm/board-htcleo-wifi-nvs.c
<4>[ 130.232330] wlan: eth0: Broadcom Dongle Host Driver mac=00:11:22:33:44:55
I even changed the default in the code (board-htcleo-wifi-nvs) but it's presumably not getting it from there now. :S
I doesn't get this working, have MDJ FroYo HD v.4.4 KERNEL: hastarin r8.5.3
RADIO: 2.15.50.14, how do i get my wifi working?!
UPDATE, replaced the *.ko files and wifi is working like a charm! Thx for fix.
Bartjuh_4 said:
I doesn't get this working, have MDJ FroYo HD v.4.4 KERNEL: hastarin r8.5.3
RADIO: 2.15.50.14, how do i get my wifi working?!
UPDATE, replaced the *.ko files and wifi is working like a charm! Thx for fix.
Click to expand...
Click to collapse
What ko files did you change?
thanks
Desire HD Builds workaround
Hi,
it seems that the Desire HD builds are using /etc/calibration instead of /proc/calibration file to get its params.
It could be that the module is loaded with module param nvram_path = /etc/calibration
in addition each time the wifi device is turned off/on, the calibration file is copied from /system/etc/calibration to /etc/calibration.
In case the MAC address param is fixed in the /system/etc/calibration every thing will work fine.
Possible fixes (as I see it, but not sure yet how to do it):
1. during system init, delete /system/etc/calibration and create a link to /proc/calibration.
1. during system init, edit the /system/etc/calibration and change the MAC address based on the cmdline.
hope this is helpful.
OSM said:
Hi,
it seems that the Desire HD builds are using /etc/calibration instead of /proc/calibration file to get its params.
Click to expand...
Click to collapse
Thanks. I'd hit the button but on my phone atm
That will be very handy. I can modify my init.kernel.sh to also update /etc/calibration from /proc/calibration or the update script to delete the file and create a symlink.
I'll definitely sort something out before releasing my next kernel update.
Sent from my HTC HD2
hastarin said:
Thanks. I'd hit the button but on my phone atm
That will be very handy. I can modify my init.kernel.sh to also update /etc/calibration from /proc/calibration or the update script to delete the file and create a symlink.
I'll definitely sort something out before releasing my next kernel update.
Sent from my HTC HD2
Click to expand...
Click to collapse
I think you should update the /system/etc/calibration, and not the /etc/calibration.
it seems that each time the wifi is enabled, the /system/etc/calibration is copied to the /etc/calibration.
ofcource you can simple copy the /proc/calibration to the /system/etc/calibration
OSM said:
I think you should update the /system/etc/calibration, and not the /etc/calibration.
it seems that each time the wifi is enabled, the /system/etc/calibration is copied to the /etc/calibration.
ofcource you can simple copy the /proc/calibration to the /system/etc/calibration
Click to expand...
Click to collapse
Thanks I've had a quick look and there are various differences between the proc and etc files, so I may start out by just updating the macaddr via the init script.
Welcome everyone to my RPi Media Center. This project is aimed at RPi 2 & RPi 3. Just a couple of things before we get started:
This project aims to explain how to set up a complete multimedia center (mediacenter), a game station and a download server. All in one. Any use aimed at hacking / stealing content with copyrights / third parties without express consent is prohibited. This project is based on a set of free software that can be easily found on the internet. This project has no lucrative purpose, its sole purpose is to teach and educate people the configuration and use of the different programs. This project was originally maintained by AikonCWD and has since stopped updating the project, so i am taking it on board to get it back up and running smoothly again. Obviously there will and are hick-ups/bugs. Thus for the mean time i will keep the project in Beta until we have a fully functional release.
For DCMA reasons Kodi will be supplied with NO EXTRA ADD-ONS. Please do not ask about them Look HERE if you are such inclined to do so. We do not condone such behavior.
Features:
-Multi-Media Center: Kodi 17.4 Krypton
-Game Center: RetroPie 4.0
-Game Streaming: Moonlight 2.2.1
-Download Center(s): Transmission & PyLoad
-Workstation: XFCE, FireFox & Chromium
-Tools: a bunch of extra tools
Needed Components:
-RPi 2 or PRi3
-MicroSD SDHC card (6gb or more recommended)
-MicroUSB Charger(5Volt and 3Amp)
-Protective enclosure for the RPi
-HDMI Cable
Recommended Extras:
-Power supply cable with the ON/OFF click button switch
-Heat sinks and fan to help keep the RPi Cooler
-Wireless Keyboard and Mouse Combo
-Xbox360 Controller (USB)
Pre-Configured for ease of use:
-Everything is pre-configured for a plug and play functionality. You shouldn't have to set anything up unless you have updated the files.
-Everything is in English, Originally translated from Spanish. (Please note i can support more languages if its needed in the future)
-Protocols SSH and SMB (Samba) are enabled (Username: root / Password: aikoncwd)
-Transmission setup for maximum torrent speeds (IT IS HIGHLY RECCOMENDED TO SET THIS UP WITH YOUR OWN Username and Password! Info on how to do that can be FOUND HERE)
-Access via Zeroconf enabled (For remote control via SmartPhone)
Whats Been Disabled for Performance Reasons:
-AirPlay
-Time Addon
-RSS news reader disabled
-Library Sharing Via UPnP
Okay Lets get started with the Installation, its pretty straight forward i have shrunk the .img as low as i can for the mean time. After Beta is done i will make more of an effort to shrink the file further.
Installation:
1. Download the preconfigured BETA-RPiMediaCenter.img image
2. Record the image on your microSD card :
-Windows : Use Win32DisKImager
-Linux :
Code:
sudo pv BETA-RPiMediaCenter.img | sudo dd of=disk2s1 bs=4M && sync
-MAC : Use the Apple-PiBakery program , thanks to jagarciavi
3. Insert your microSD with the .IMG that we loaded on to the SD-Card In the previous step
4. Plug in the power
5. The Raspberry will light up (Red/Green LED's on the mainboard) and the start up splash will show.
7. RPi Media Center will start automatically at boot every time.
8. (Optional) Verify that the partition occupies 100% of your microSD with the command:
Code:
df -h
MD5 CHECK-SUM:
Code:
921d4d195a795ddef00cf221160836f6
*Verify on windows with this TOOL
After Install
It is recommended that you set-up a static IP for your Media Center. It makes things a whole lot easier if you're using Moonlight and Transmission.
Which can be done by:
Opening Terminal and Typing
Code:
nano /etc/dhcpcd.conf
Then removing # From each of these lines:
Code:
interface eth0
static ip_address=192.168.1.100/24
static routers=192.168.1.1
static domain_name_servers=8.8.8.8
And then setting up as to how you need it to. Its different for everyone.
Extras Install Guide:
Configure PyLoad (optional)
PyLoad is a program that allows you to transform your Raspberry into a direct download server . The PyLoad daemon is installed and configured, but it is disabled by default since not all users need to use it. If you want to enable and use PyLoad ... keep reading:
First of all we are going to configure the daemon so that it is auto-executed when turning on the Raspberry . Edit the cron auto-boot file with the command:
Code:
crontab -e
We are located at the bottom, locate the line @reboot pyLoadCore -daemonand remove the comment from the beginning, it should look like this: @reboot pyLoadCore --daemon( you have to put the 2 dashes in front of the word daemon ). Save the changes by pressing the keys: CTRL+ X, then Yand finallyIntro
You will have to restart your Raspberry to have the pyLoad daemon running, remember that Kodi turns on automatically, you must close it to return to the console.
We access PyLoad through a web browser using port 8000 , for example: http://192.168.1.100:8000
The default user is root and password root . In the top menu you can manage the user and change the password (recommended), just below you will find the configuration where you can edit the configuration, captchas plugins etc ... and add any premium account you have from the different hosts.
Overclocking (optional) DO SO AT YOUR OWN RISK!
I recommend enabling a bit of overclock , you'll get more fluency when moving through the Kodi menus and you'll noticeably boost performance when playing emulators. Your CPU will be able to perform faster calculations and access to ram memory or microSD disk will have lower response times.
Strongly recommend use some method of ventilation / cooling in order to avoid reaching 85C , since the RPI lower speed if it reaches that temperature
If you want you can run a benchmark (diagnostic) to test your overclock level, execute the following command:
Code:
curl [url]https://raw.githubusercontent.com/aikoncwd/rpi-benchmark/master/rpi-benchmark.sh[/url] | sudo bash
Raspberry Pi 3: Overclock settings
Edit your file nano /boot/config.txtand paste the following code, you can adjust the values to have more or less overclock:
Code:
force_turbo=0 #Enable cpu-overclock over 1300MHz (default 0)
avoid_pwm_pll=1 #Enable no-relative freq between cpu and gpu cores (default 0)
arm_freq=1300 #Frequency of ARM processor core in MHz (default 1200)
core_freq=550 #Frequency of GPU processor core in MHz (default 400)
over_voltage=6 #ARM/GPU voltage adjust, values over 6 voids warranty (default 0)
sdram_freq=575 #Frequency of SDRAM in MHz (default 450)
sdram_schmoo=0x02000020 #Set SDRAM schmoo to get more than 500MHz freq (default unset)
over_voltage_sdram_p=6 #SDRAM phy voltage adjust (default 0)
over_voltage_sdram_i=4 #SDRAM I/O voltage adjust (default 0)
over_voltage_sdram_c=4 #SDRAM controller voltage adjust (default 0)
gpu_mem=256 #GPU memory in MB. Memory split between ARM and GPU (default 64?)
gpu_freq=550 #Sets core_freq h264_freq isp_freq v3d_freq together (default 300)
v3d_freq=500 #Frequency of 3D block in MHz (default ?)
h264_freq=350 #Frequency of hardware video block in MHz (default ?)
dtparam=sd_overclock=75 #Clock in MHz to use for MMC micrSD (default 50)
dtparam=audio=on #Enables the onboard ALSA audio (always use this ON)
dtparam=spi=on #Enables the SPI interfaces (default OFF)
temp_limit=80 #Overheat protection. Disable overclock if SoC reaches this temp
initial_turbo=60 #Enables turbo mode from boot for the given value in seconds
hdmi_drive=2 #Normal HDMI mode. Sound will be sent if supported and enabled (default 2)
hdmi_ignore_cec_init=1 #Avoids bringing TV out of standby and channel switch when booting (default 0)
hdmi_ignore_cec=0 #Pretends CEC is not supported. No CEC functions will be supported (default 0)
hdmi_force_hotplug=1 #Pretends HDMI hotplug signal is asserted (default 0)
start_x=1 #Enable software decoding (MPEG-2, VC-1, VP6, VP8, Theora, etc. default 0)
overscan_scale=1 #Video Output will respect the overscan settings (default 1)
disable_overscan=0 #Disable overscan configuration. Set 1 if you see black lines on TV (default 0)
disable_splash=1 #Avoids the rainbow splash screen on boot (default 0)
avoid_warnings=1 #Disable warnings (Red=over-temperature ; Rainbow=under-voltage). (default 0)
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256
Read the commands well, you may want to modify some to customize your image.
Raspberry Pi 2: Overclock settings
Edit your file nano /boot/config.txtand paste the following code, you can adjust the values to have more or less overclock:
gpu_mem=256
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256
arm_freq=1100
core_freq=550
sdram_freq=483
over_voltage=6
over_voltage_sdram=2
temp_limit=70
force_turbo=0
initial_turbo=60
hdmi_drive=2
hdmi_ignore_cec=0
hdmi_ignore_cec_init=1
hdmi_ignore_hotplug=0
hdmi_force_hotplug=1
#disable_overscan=0
#overscan_scale=1
#overscan_left=49
#overscan_right=49
#overscan_top=29
#overscan_bottom=25
max_usb_current=1
dtparam=audio=on
dtparam=spi=on
You will find a script called bcmstat that allows you to accurately measure the hardware status of your Raspberry, you can see at what speed your CPU is going and at what temperature it is, for this it executes:
/root/bcmstat.sh
MoonLight
*Coming Soon*
DOWNLOADHERE
Download Option#2
Credits:
AikonCWD for his amazing original work
@Valkiry for continuing the development
BUGS
-Desktop/Emulationstation and wifi addons are currently not working.
Just use These commands for what you need when it goes to the terminal:
Desktop Environment:
Code:
startx
RetroPie:
Code:
emulationstation
Wifi
Code:
./RetroPie-Setup/retropie_packages.sh 829 gui
Bluetooth
Code:
./RetroPie-Setup/retropie_packages.sh 803 gui
I will fix these at a later date But for the mean time let me know how you go
Raspberry Pi Mediacenter
Hi. The previous version from AikonsCWD impressed. I was looking for ways to update KODI on Krypton, found your topic. Thanks for the update, but the scripts do not work, the command line falls out. Are there plans to upgrade from beta? I was looking for a way to cross Raspbyan XFCE and KODI, but really nothing happened. Do not tell me how to update or build your image? Thank you.
P.S. English is not my favorite language.
AlexFBG said:
Hi. The previous version from AikonsCWD impressed. I was looking for ways to update KODI on Krypton, found your topic. Thanks for the update, but the scripts do not work, the command line falls out. Are there plans to upgrade from beta? I was looking for a way to cross Raspbyan XFCE and KODI, but really nothing happened. Do not tell me how to update or build your image? Thank you.
P.S. English is not my favorite language.
Click to expand...
Click to collapse
Thanks for your feedback, I'm looking at updating it this year but I'm not sure when that will occur. The scripts don't work as stated. If you exit out of kodi you will be met with the command line which is where you run said commands to get them to work. Kodi is updating to 18 later this year so I might update the project to support 18 and the scripts till then this runs as intended.
Hello and thanks for the effort!
Although the image is working fine in my RP2+, I tried it into an RPB3+ and looks the OS is not booting.
Any idea what's happening? I tried default values and also overclock values, neither is making bootstrapping the OS.
kikobeats said:
Hello and thanks for the effort!
Although the image is working fine in my RP2+, I tried it into an RPB3+ and looks the OS is not booting.
Any idea what's happening? I tried default values and also overclock values, neither is making bootstrapping the OS.
Click to expand...
Click to collapse
It's not for 3b+.
Only RPi2/3/3B
Hello everyone.
I have a Japanese S6 Edge (404SC). So I tried to install a custom rom in this phone as the support has ended. I can install the rom with no problem and it would boot up until the initial welcome screen.HOWEVER the touchscreen would just not work. So I asked the developer and he told me that the touch configs of my phone is different than the other S6’s. So can someone please explain to me how to change the touch configuration of this phone while compiling the kernel to make the touchscreen work again.BTW,I also couldn’t find any guide regarding this issue. Thank you.
@mikel05
You don't have to compile anything.
Built-in embedded devices, particularly touch screens, almost always require input device configuration (.IDC - plain text ) files to specify their behavior.
Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name.
The following paths are consulted by stock Android in order
/odm/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/odm/usr/idc/Vendor_XXXX_Product_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX.idc
/odm/usr/idc/device-name.idc
/vendor/usr/idc/device-name.idc
/system/usr/idc/device-name.idc
/data/system/devices/idc/device-name.idc
Example of an .IDC file
Code:
# This is an example of an input device configuration file.
# It might be used to describe the characteristics of a built-in touch screen.
# This is an internal device, not an external peripheral attached to the USB
# or Bluetooth bus.
device.internal = 1
# The device should behave as a touch screen, which uses the same orientation
# as the built-in display.
touch.deviceType = touchScreen
touch.orientationAware = 1
# Additional calibration properties...
# etc...
jwoegerbauer said:
@mikel05
You don't have to compile anything.
Built-in embedded devices, particularly touch screens, almost always require input device configuration (.IDC - plain text ) files to specify their behavior.
Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name.
The following paths are consulted by stock Android in order
/odm/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/odm/usr/idc/Vendor_XXXX_Product_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX.idc
/odm/usr/idc/device-name.idc
/vendor/usr/idc/device-name.idc
/system/usr/idc/device-name.idc
/data/system/devices/idc/device-name.idc
Example of an .IDC file
Code:
# This is an example of an input device configuration file.
# It might be used to describe the characteristics of a built-in touch screen.
# This is an internal device, not an external peripheral attached to the USB
# or Bluetooth bus.
device.internal = 1
# The device should behave as a touch screen, which uses the same orientation
# as the built-in display.
touch.deviceType = touchScreen
touch.orientationAware = 1
# Additional calibration properties...
# etc...
Click to expand...
Click to collapse
Thank you @jwoegerbauer for your explanation.
So now to install the custom ROM where must I change these values. Like where are these files located
I'm really so sorry for asking this as I am still new to this.
@mikel05
Search the device for a file with extension idc: if not present then it got deleted when you flashed a new ROM and you're out of luck.
jwoegerbauer said:
@mikel05
Search the device for a file with extension idc: if not present then it got deleted when you flashed a new ROM and you're out of luck.
Click to expand...
Click to collapse
Actually the touchscreen works in the stock rom properly. It only doesn’t work in custom rom and kernels.
@ jwoegerbauer
Sorry for not informing earlier. My bad.