Develop Bugs

Build.Prop item description

I want to know Build.prop every item mean and had searched all over, but only found one page http://www.streakdroid.com/wiki/index.php?title=Build.prop, unfortunally, this page not contain all items, for example:
ro.telephony.default_network
0 = WCDMA Perfered
1 = GSM Only
2 = WCDMA Only
3 = GSM/WCDMA (auto mode, according to PRL)
4 = CDMA / EVDO. Perfered
ro.setupwizard.mode
OPTIONAL = Allow bypass of first start setup
DISABLED = Do not show setup on first start
Click to expand...
Click to collapse
http://www.neopeek.com/viewtopic.php?f=14&t=6313&start=300
Here is other page that mention build.prop
Suggestions, in build.prop try the following and test:
ro.product.cpu.abi=armeabi-v7 [remove or change to] ro.product.cpu.abi2=armeabi-v7 [or] ro.product.cpu.abi2=armeabi-v7a
Technically these shouldn't even be used [keep] ro.product.cpu.abi=armeabi
ro.board.platform=qsd8k [remove]
we have an msm7k not qsd8k [keep] ro.board.platform=msm7k
Only "ro.opengles.version = 65536" is needed as 131072 is for EGL2.0
AFAIK 65536 = EGL 1.0, 65537 = EGL 1.1, 131072 = EGL 2.0
and the version in your libGLES_qcom.so is "OpenGL ES 1.0-CM"
Click to expand...
Click to collapse

Lots of interest in build.prop lately.
Your best option may be to just search on each setting, a lot of people on xda and elsewhere have discussed most of the settings.
What settings do you have questions about specifically?
EDIT: It is also worth noting that build.prop is not the only place some of these settings are located. Some of the more important settings are configured elsewhere using detection routines. (these settings supercede the settings entered in build.prop.)
Not all phones are the same or use the same settings, builds like xdandroid are put together with this in mind.

nice, job
the most important when making, mod builds, build a new ROM, change anything in the system.ext2. IT'S THE END RESULTS. I use this in all my mod builds. notice on the market when looking for and app and the app is not there.
add this to your build.prop. ro.product.cpu.abi=armeabi-v7. you will see a lot more apps. we know this is not for our devices. but we have to try to get the best possible results for everyone. look this is what the new BLAZN build will have. with this and others stuff it runs super fast.
ro.product.cpu.abi=armeabi
ro.product.cpu.abi=armeabi-v7
ro.board.platform=msm7k
ro.board.platform=qsd8k
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 65536
ro.opengles.version = 131072
#0 - mdp composition, 1 - gpu composition
ro.sf.hw=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.ril.hsxpa=3
ro.ril.gprsclass=32
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=28
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.hsupa.category=9
rild.libargs=-d /dev/smd0
DEVICE_PROVISIONED=1
ro.config.hw_addsettingsdbex=1
ro.config.hw_gcf_mms=true
ro.config.hwft_PNN_function=true
persist.cust.tel.adapt=1
persist.cust.tel.eons=1
ro.config.hwfeature_gps_test=0
ro.config.hwfeature_ecc=true
keyguard.no_require_sim=true
ro.config.lowbattery_shutdown=1
ro.config.hwfeature_wakeupkey=1
ro.config.endkeybehavior=true
ro.config.hw_menu_unlockscreen=false
ro.config.KeyPassToUser=true
ro.media.enc.lprof.duration=30
ro.config.PicMaxSize=3mp
ro.config.hw_temperature_warn=true
ro.config.hw_clocksetting=0
#set network mode CDMA-->4 WCDMA-->0
ro.telephony.default_network=0
ro.cdma.home.operator.numeric=
# Release Bluetooth HW/SW information
ro.bt.chipset = Broadcom BCM4329-B1
ro.bt.version = Bluetooth 2.1 + EDR
ro.bt.stack = Broadcom BTL-A
ro.bt.stack.version = 2.0.50.032
#0x10000010010100100000011 represent bt profile list
ro.bt.profiles = 4270339
# Properties of BTLA stack
service.brcm.bt.activation = 0
service.brcm.bt.srv_active = 0
service.brcm.bt.hcid_active = 0
service.brcm_bt.btld = 0
service.brcm.bt.btld_pid = 0
service.brcm.bt.avrcp_pass_thru = 0
service.brcm.bt.avrcp_toggle = 1
# froyo 2.2.1 blazn add prop
#DTS2010082701201 liyou 20100827 begin
ro.config.hwft_MatchNum=7
#ro.config.hwft_MatchNumShort=7
#DTS2010082701201 liyou 20100827 end
ro.product.factoryversion=0
# 0:nothing; 1:go home; 2:go sleep; 3:go home and then sleep.
ro.config.hw_defaultEndBtnFunc=1
ro.config.hwft_PinPukUnlockscr=true
ro.com.google.clientidbase=hw-smart-phone
ro.config.hw_opta=
ro.config.hw_optb=
ro.config.hw_temperature_warn=true
ro.config.hw_ignore270=true
ro.config.hw_timeformat=true
ro.config.timeformat=24
ro.config.hw_dateformat=true
ro.config.dateformat=dd-MM-yyyy
# DTS2010073101355 wangqing 20100806 end
ro.config.hw_gl=1
#
# QUAIL MODS
#
# UI Tweaks
#ro.config.hw_default_launcher=org.zeam
#ro.config.hw_isCustomize=true
#ro.config.hw_customizeType=02
#ro.config.PopupTwink=true
#ro.config.SetStatusbarText=true
ro.config.hw_boot_animation=true
ro.setupwizard.mode=DISABLED
# Automatically turn display off when idle.
settings.display.autobacklight=true
# To make the phone ring faster when dialing out, I changed
ro.telephony.call_ring.delay=1000
# To make the phone come off of the "black screen" faster in the middle of
# or the end of phone calls when you pull the phone away from your face.
mot.proximity.delay=100
# To enable the hard key lights to stay on while the screen is on and not timeout
ro.mot.buttonlight.timeout=false
# Google has something called a "checkin" service that sends them anonymous
# usage data, bug reports, crash logs, etc, but it fails a lot. When you download
# something from the Market, it sends a message to Google about it, and if it fails
# it just freezes.
ro.config.nocheckin=true
ro.ril.def.agps.mode=1
ro.ril.def.agps.feature=1
ro.ril.enable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=1
ro.ril.enable.gea3=1
ro.ril.disable.power.collapse=0
ro.telephony.call_ring.delay=1
ro.config.notification_sound=DearDeer.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.config.ringtone=BussaMove.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.setupwizard.mode=OPTIONAL
ro.media.dec.jpeg.memcap=10000000
rild.libpath=/lib/froyo/libhtcgeneric-ril.so
ro.compcache.default=18
wifi.supplicant_scan_interval=120
ro.sf.lcd_density=210
ro.telephony.default_network=0
# Dalvik VM heap size
dalvik.vm.heapsize=32m
dalvik.vm.execution-mode=int:fast
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
the build.prop is not the only place some of these settings are located. I always look for the best possible results for everyone
THANKS

very good, thanks tiad8, I learn more from your post.
I notice you add bluetooth section,does this mean android support rhod400 bt now?
ok, I know this from your blazn post
Nautis said:
EDIT: It is also worth noting that build.prop is not the only place some of these settings are located. Some of the more important settings are configured elsewhere using detection routines. (these settings supercede the settings entered in build.prop.)
Click to expand...
Click to collapse
Yes, i had noticed this,when I change locale to chinese, only setupwizard is chinese language, system locale need to set at settins->languages
ro.product.locale.language=zh
ro.product.locale.region=CN

[Q] Ingress (Niantic Project) on Kindle Fire MoDaCo Gr9 (6.3.1)

Does anyone know why the Niantic Labs app Ingress (V1.00.0) will not work on the Kindle Fire 1st gen with MoDaCo Gr9 [ROM]? After selecting an account, it goes to the v1.00.0 splash screen and then flashes the SCAN screen before force closing.
The Niantic Labs app Field Guide (V1.06) works fine and they have the same version requirements and similar permission requirements. I do see that version 1.06 of Field Guides had the following update: "Fixed crashes for selected devices." Surely they wouldn't release the initial version of ingress with the same issue?

It looks like it may be an issue with the lack of gps. I was hoping this wasn't the case since gr9 enables coarse location based on the network. The Field Trip app works perfectly fine using the coarse network location but perhaps Ingress doesn't like this?
A portion of the logcat is attached as log3.txt. If this log is missing some important pieces, let me know and I can attach more.
Here are some incriminating snippets: (see the attachment for more)
E/AndroidRuntime( 7381): FATAL EXCEPTION: LocationTracker
E/AndroidRuntime( 7381): java.lang.IllegalArgumentException: provider=gps
"E/AndroidRuntime( 7381): at android.os.Parcel.readException(Parcel.java:1326)"
"E/AndroidRuntime( 7381): at android.os.Parcel.readException(Parcel.java:1276)"
"E/AndroidRuntime( 7381): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)"
"E/AndroidRuntime( 7381): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:582)"
"E/AndroidRuntime( 7381): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:446)"
"E/AndroidRuntime( 7381): at com.niantic.nemesis.sensors.c.c(SourceFile:40)"
"E/AndroidRuntime( 7381): at com.niantic.nemesis.sensors.f.run(SourceFile:255)"
"E/AndroidRuntime( 7381): at android.os.Handler.handleCallback(Handler.java:587)"
"E/AndroidRuntime( 7381): at android.os.Handler.dispatchMessage(Handler.java:92)"
"E/AndroidRuntime( 7381): at android.os.Looper.loop(Looper.java:130)"
"E/AndroidRuntime( 7381): at android.os.HandlerThread.run(HandlerThread.java:60)"
W/ActivityManager( 1395): Force finishing activity com.nianticproject.ingress/com.niantic.nemesis.NemesisActivity
I/AndroidComm( 7381): onLoadFinished
Click to expand...
Click to collapse
Feel free to elaborate if you guys know of a solution or work-around (without trying to tether a gps from another android device... I don't have one).
(Ps: I would love for this to be in the "Amazon Kindle Fire > Kindle Fire Android Development > [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire" thread but, alas, I do not have 10 posts.)

Ummm yeah, there's no GPS on the Kindle Fire. It's missing a lot of sensors.. It's a eBook reader. Even if root/hacked/ROMd

icebrkr said:
Ummm yeah, there's no GPS on the Kindle Fire. It's missing a lot of sensors.. It's a eBook reader. Even if root/hacked/ROMd
Click to expand...
Click to collapse
I'm well aware of this. I was wondering if anyone had any success getting it to work with coarse network location identification, alone.

anywhose said:
I'm well aware of this. I was wondering if anyone had any success getting it to work with coarse network location identification, alone.
Click to expand...
Click to collapse
So I don't know if you are saying it crashes or doesn't work, but I am running twa_priv's cm10 jellybean ROM, and I installed the app. When I launched it, it opened fine, but since I didn't (and still don't) have the acces code to participate yet, I can't tell you if it doesn't work or not. Does google Maps work for you? it works on the ROM I am running. More specifically, the location part of Google Maps...

jma9454 said:
So I don't know if you are saying it crashes or doesn't work, but I am running twa_priv's cm10 jellybean ROM, and I installed the app. When I launched it, it opened fine, but since I didn't (and still don't) have the acces code to participate yet, I can't tell you if it doesn't work or not. Does google Maps work for you? it works on the ROM I am running. More specifically, the location part of Google Maps...
Click to expand...
Click to collapse
The location part of Google Maps works fine and so does the Field Trip app by niantic projects. I mention the Field Trip app because it also seeks a gps signal but when it does not detect gps hardware, it uses the coarse network location.
For me, the app works fine until you enter the access code. At this point, it tries to locate your position and force crashes.

Google Now Voice Search kills Voice Search Systemwide

Hi all,
i've got an odd issue and wonder if somebody else has this.
I'm on pabx' AOSP ROM rc19.
When using Voice Search in Google Now it works the first time. After switching to another app and returning Voice Search fails with something like "Could not be understood". It fails immediately and doesn't even try to record anything.
PLUS: at this point voice recording fails in any app (e.g android voice input / swiftkey, what so ever).
when i force kill Google Search App, everything works again. so this somehow seems to block voice input.
maybe someone can reproduce this..
here's my logcat..
Code:
W/AudioFlinger( 193): findSuitableHwDev_l() loading well know audio hw modules
W/AudioFlinger( 193): loadHwModule() module primary already loaded
W/AudioFlinger( 193): loadHwModule() module a2dp already loaded
E/AudioFlinger( 193): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 193): loadHwModule() error -2 loading module usb
E/AudioRecord(10035): Could not get audio input for record source 6
E/AudioRecord-JNI(10035): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java(10035): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
D/dalvikvm(10035): GC_FOR_ALLOC freed 455K, 16% free 15471K/18248K, paused 28ms, total 28ms
I/dalvikvm-heap(10035): Grow heap (frag case) to 15.439MB for 320016-byte allocation
D/dalvikvm(10035): GC_FOR_ALLOC freed 7K, 16% free 15776K/18564K, paused 27ms, total 27ms
I/AudioService( 576): AudioFocus requestAudioFocus() from [email protected][email protected]
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(10035): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
I/VS.G3EngineManager(10035): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 3 ms
I/decoder (10035): ERROR: Exception thrown from GoogleRecognizer.read()
W/System.err(10035): java.io.IOException: AudioRecord failed to initialize.
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
W/System.err(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
W/System.err(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
W/System.err(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
W/System.err(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
W/System.err(10035): at java.io.InputStream.read(InputStream.java:163)
W/System.err(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
D/dalvikvm(10035): threadid=49: thread exiting, not yet detached (count=0)
E/VS.G3EngineManager(10035): Error running recognition: 3
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/AudioService( 576): AudioFocus abandonAudioFocus() from [email protected][email protected]
E/UberRecognizerController(10035): onError
E/UberRecognizerController(10035): com.google.android.speech.exception.AudioRecognizeException: Audio error
E/UberRecognizerController(10035): at com.google.android.speech.embedded.Greco3Recognizer.read(Greco3Recognizer.java:98)
E/UberRecognizerController(10035): at dalvik.system.NativeStart.run(Native Method)
E/UberRecognizerController(10035): Caused by: java.io.IOException: AudioRecord failed to initialize.
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
E/UberRecognizerController(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
E/UberRecognizerController(10035): at java.io.InputStream.read(InputStream.java:163)
E/UberRecognizerController(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
E/UberRecognizerController(10035): Got error after recognizing []

I had exactly the same thing few weeks ago on a number of roms, couldn't get a fix so just settled on a rom that didn't have the issue
Sent from my HTC One X using xda premium

Thanks for your reply.
can you tell me on which roms you experienced the issue and on which it does not occur?
on AOKP it doesn't work either.
Sense ROMs seem to be working..
I also sent a feedback report to google but i don't think there will be any response.

It worked on sense ROMs but I don't like them, most aokp and aosp ROMs had the the problem but for some reason it works fine on xenonhd and slimbean. I like slim so I just stuck with it
Sent from my HTC One X using xda premium

I digged in a little bit deeper and it's really odd.
on the first launch google now initializes in my local language:
Code:
I/VS.G3EngineManager(23710): create_rm: m=ENDPOINTER_VOICESEARCH,l=de-DE
I/VS.G3EngineManager(23710): Brought up new g3 instance :/data/data/com.google.android.googlequicksearchbox/app_g3_models/de-DE/endpointer_voicesearch.config for: de-DEin: 34 ms
which works.
after returning it tries to bring up
Code:
I/VS.G3EngineManager(30287): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
W/Search.ConcurrentUtils(30287): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(30287): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 2 ms
I/decoder (30287): ERROR: Exception thrown from GoogleRecognizer.read()
which than fails.
when setting the system language to english it works all the time.
Do you still use a different language than EN_US on SlimBean (I suppose you did) ? or might that be the reason it is working on Slim ?

Phone and search are set to eng UK. Just tried changing to eng generic on Google now and the problem returns, changed back to eng UK and still problem then cleared app cache in system setting and all is fine again. So looks like you found something, good job
Sent from my HTC One X using xda premium

thanks for trying.
would be awesome if someone with a sense rom could try as well.
But i guess it will be an AOSP / 4.2.2 issue only.
maybe one of the dev's can have a look into it.. would be awesome to get this one figured out.

seems like the latest google search / now update solved the problem for me.
maybe you can confirm !?

Asus music app random stops?

I'm having a issue with the Asus Music app which is when I'm in other apps it likes to stop randomly where I have to press play again until twenty seconds later to a another stop. I have a ZenFone 2e flashed with stock ZenFone 2 118 firmware.
Any help is welcome.
Sent from my Z00D using XDA Free mobile app

Any help is welcomed and if anyone wants to, I used Advanced Logcat Viewer to make a logcat log.
Also, I took a look and these few lines are from start of Chipzel's Courtesy and then into ManDoPony's -Just Gold- song, stopped with a buzz connected to my laptop in mic port on listen to this device, how I'm trying to debug this.
Code:
V/AsusMusicService.Player(12194): [AsusPlayer] Play: chipzel---courtesy-(a.-aaa)
E/NetlinkEvent(252): NetlinkEvent::FindParam(): Parameter 'TIME_NS' not found
E/MediaPlayer(856): Should have subtitle controller already set
E/NetdConnector(699): RCV <- {613 IfaceClass idle (null)}
D/Ringtone(856): Successfully created local player
E/NetdConnector(699): Error handling '613 IfaceClass idle (null)': java.lang.NumberFormatException: Invalid int: "(null)"
D/NuPlayerDriver(248): reset(0xb080c220)
V/AlarmManager(699): triggered: act=com.android.internal.telephony.data-stall Pkg: com.android.phone
D/NuPlayerDriver(248): notifyResetComplete(0xb080c220)
D/PowerManagerNotifier(699): onWakeLockAcquired: flags=1, tag="*alarm*", packageName=android, ownerUid=1000, ownerPid=699, workSource=WorkSource{1001}
D/NuPlayerDriver(248): reset(0xb080c220)
D/PowerManagerNotifier(699): onWakeLockReleased: flags=1, tag="*alarm*", packageName=android, ownerUid=1000, ownerPid=699, workSource=WorkSource{1001}
V/AudioFlinger(248): acquiring 290 from 856, for -1
D/PowerManagerService(699): updateIsPoweredLocked: wasPowered=true, mIsPowered=true, oldPlugType=2, mPlugType=2, mBatteryLevel=73
V/AudioFlinger(248): added new entry for 290
W/BatteryStatsImpl(699): Couldn't get kernel wake lock stats
V/AudioFlinger(248): releasing 289 from 856 for -1
D/PowerUI (856): dismiss Low BatteryWarning level: 73
V/AudioFlinger(248): decremented refcount to 0
D/PowerUI (856): show_hot_plug_dialog: true
V/AudioFlinger(248): purging stale effects

JeeLight - ultimate Yeelight experience

Think of JeeLight as being the ultimate Yeelight experience for PC – whether you need ambient lighting for your office, a powerful Ambilight Mode that enhances immersion, or creating scenes and lighting presets for hosting parties, JeeLight can do everything you need.
Yeelights are the cheapest and best alternative to the expensive Phillips Hue!
JeeLight’s Core Features:
Real Ambilight (“Ambilight creates light effects that correspond to the screen content.”)
The capturing Zones can be set up individually for each Light by drag&drop.
Flash detection (adds immersion to scenes with flashing lights)
CPU Multithreading (experimental)
Detect average or predominant colors – results vary depending on screen content.
Zone testing (launches a video to quickly test and configure your JeeLight zones)
Playground
Set each Yeelight (or all together) to your favorite color.
Mouseflow tracks your mouse cursor and changes your Yeelights to whatever you’re mousing over.
Effectcreator
Create your own effects. Easy as 1-2-3
Sceneplayer
Play Presets or our own Effects created in Effectcreator
Set different Effects to different Lights and play them at the same time
Upload your custom Effect to the community Server
Download other custom Effects and use or edit them
Specials
Roompaint
With this mode all colors will flow slowly from one Light to the next one. And paint your room with uncountable beautiful colors.
Twinkle
Circadian Lighting (like f.lux) a lighting system designed to tap into the cycles our bodies’ follow each day, based on the color of the sky.
Runs on Windows, MacOS and Linux
Supports all WiFi enabled YeeLights!
Here a short demonstration of Ambilight. This video shows the first running version. Since then many improvements and functions have been added!
Please Note:
There is a Firmware issue in Yeelight bulbs which cause flickering due to high Framerate in Ambilight. I am in contact with Yeelight and there will be a Firmware update soon. Users of the beta firmware are able to activate the new feature (Send Beta Commands).
The software is in a final beta state and may not yet be working as expected – please report any bugs encountered in the forum. Furthermore its only tested on Windows, but should work on other OS too.
You need to enable “LAN-Control” in the Yeelight app for each Light.
JeeLightis free. However, I would be happy to accept small donations.This will help me to pay my hardware and server costs, as well the huge amount of coffee which is needed to develop more crazy stuff. (there’s a lot of nightly hours . Each donator will become a Beta-tester and receive every new function at first.
You can use the installer for Windows and MacOS which already includes the Java runtime. Of course you can use the JAR file too.
For Linux you have to download the latest Java Runtime and start the JAR File
Also check out the Guide!
Visit the Community forum and make some feature requests!
If you dont have any Yeelights yet, you can get yours following the Affiliate Links
YeeLight color Bulb V1
YeeLight color Bulb v2
YeeLight Strip 2m
Yeelight Bedside Lamp
Download JeeLight here!

Just downloaded and tested it on my 3 lights (2 bulbs + 1 strip). It works great, here's my notes so far:
1 - CPU usage is about 20% average on an AMD A8-5600k. I'm curious how you only get 3-8% on your setup.
2- Once you click "Start", the Jeelight app becomes very slow/unresponsive until you click "Stop". Only the Jeelight app, the computer runs normal.
3- A 3 minute time-limit on a beta demo is kind of...meh. Its not enough time to really test the app in movies, games, etc.
In any case, great work so far, I look forward to seeing this developed more

Akti88 said:
Just downloaded and tested it on my 3 lights (2 bulbs + 1 strip). It works great, here's my notes so far:
1 - CPU usage is about 20% average on an AMD A8-5600k. I'm curious how you only get 3-8% on your setup.
2- Once you click "Start", the Jeelight app becomes very slow/unresponsive until you click "Stop". Only the Jeelight app, the computer runs normal.
3- A 3 minute time-limit on a beta demo is kind of...meh. Its not enough time to really test the app in movies, games, etc.
In any case, great work so far, I look forward to seeing this developed more
Click to expand...
Click to collapse
Thank you for your opinion and test.
1. as i see on speed rankings, your CPU is on 460th while my is on 92th. The CPU load is also depending of the size of each capture zone
2. On my PC you notice only very slight and short jerking every 300ms when you move the window. Actually, hardly worth mentioning. think the same problem as point one. i will try to outsource a part to a new thread in the next version.
3. Yeah youre right.. I will increase the time to 15-20min i think.

Blueray88 said:
Thank you for your opinion and test.
1. as i see on speed rankings, your CPU is on 460th while my is on 92th. The CPU load is also depending of the size of each capture zone
2. On my PC you notice only very slight and short jerking every 300ms when you move the window. Actually, hardly worth mentioning. think the same problem as point one. i will try to outsource a part to a new thread in the next version.
3. Yeah youre right.. I will increase the time to 15-20min i think.
Click to expand...
Click to collapse
Ohhh point 1 and 2 make perfect sense, I have a large screen and created 3 zones that use the entire screen (top left half, top right half, bottom full width). Will test again with smaller zones
Update: Yes that was exactly the problem, with smaller zones my CPU usage dropped significantly and the app doesn't jerk around anymore when being moved around. Haha, makes perfect sense. :good:

Akti88 said:
Update: Yes that was exactly the problem, with smaller zones my CPU usage dropped significantly and the app doesn't jerk around anymore when being moved around. Haha, makes perfect sense. :good:
Click to expand...
Click to collapse
Nice.
A real ambilight like from phillips or other systems out there only use 1-2 centimeters on the sides, because you want that the colors "flow out of the screen" xD
Its a heavier process to find the average color of a 1000x1000 picture instead of a 200x200 one.
Anyway I upload Version 1.5 right now with new settings. like Flashdetection and Threading Mode.
Please look in 10 minutes if version 1.5 already exist

Blueray88 said:
Nice.
A real ambilight like from phillips or other systems out there only use 1-2 centimeters on the sides, because you want that the colors "flow out of the screen" xD
Its a heavier process to find the average color of a 1000x1000 picture instead of a 200x200 one.
Anyway I upload Version 1.5 right now with new settings. like Flashdetection and Threading Mode.
Please look in 10 minutes if version 1.5 already exist
Click to expand...
Click to collapse
Nice! Small problem with 1.5 though or maybe its just me?
I uninstalled 1.4 and installed 1.5 - after that, only 2 of my 3 lights will change color, the 3rd light just stays white.
So I deleted all the zones and tried to "Discover Lights" again but now it just stays on "Searching".
Update: Nevermind, I turned the lights on and off again in the Yeelight app and Jeelight instantly found them again. Weird. And after creating new zones, they all work again.
Very nice to add hyperthreading and flash detection
I have just one small feature request, would it be possible to name the lights in the Jeelight? Currently I move colors around my screen to figure out which zonebox controls each light

Version 1.5 is online:
threading mode wich controls all lights simultaneously due Hyperthreading
brightness control
flash detection wich may give a Action szene more effects and immersion. If huge brightness difference is detected, the light will switch to full white for a fraction of a second. This is the first version and i have to deal with the values a bit more

Akti88 said:
Update: Nevermind, I turned the lights on and off again in the Yeelight app and Jeelight instantly found them again. Weird. And after creating new zones, they all work again.
Click to expand...
Click to collapse
Yeah sometimes the Yeelights no longer response to any commands. I think this is a Firmware problem.
Akti88 said:
I have just one small feature request, would it be possible to name the lights in the Jeelight? Currently I move colors around my screen to figure out which zonebox controls each light
Click to expand...
Click to collapse
Yes thats a nice Idea, i will do this

p.s: You dont have to uninstall the old version.
And to reduce your downloaddata, just download the Jar file and replace it with the Jar in your installationfolder
C:\Program Files\JeeLight\app

Very much looking forward to future development on this app (and a paid full version ). I'm putting together a guide soon for maximizing Yeelight enjoyment on PC (for a tech how-to website) so this app will definitely be included along with Yeelight Toolbox
I've been testing various methods of getting a "Music Mode" on PC, Yeelight Toolbox works great for 1 light, and his Yeelight Music Android app can be ran inside an Android emulator on PC but that only gives a disco/strobe effect to all the lights, no color matching, so I'm looking forward to testing Jeelight with a visualizer plug-in for Foobar. Normally I run Milkdrop visualizer in full-screen mode so this should be fun I think with your flash detection, it should be pretty awesome.

Akti88 said:
Very much looking forward to future development on this app (and a paid full version ). I'm putting together a guide soon for maximizing Yeelight enjoyment on PC (for a tech how-to website) so this app will definitely be included along with Yeelight Toolbox
I've been testing various methods of getting a "Music Mode" on PC, Yeelight Toolbox works great for 1 light, and his Yeelight Music Android app can be ran inside an Android emulator on PC but that only gives a disco/strobe effect to all the lights, no color matching, so I'm looking forward to testing Jeelight with a visualizer plug-in for Foobar. Normally I run Milkdrop visualizer in full-screen mode so this should be fun I think with your flash detection, it should be pretty awesome.
Click to expand...
Click to collapse
maybe in the last step JeeLight will become a full control Software, wich include the same things. But for that i need much more people with awesome ideas...And of course time

I made a short video testing Jeelight 1.5 - 3 lights (1 strip, 2 bulbs), flashing detection enabled, Rammstein concert in Paris (lots of pyrotechnics)
https://youtu.be/wmvzuRhh8BM

Updated Jeelight to v1.8!
Awesome new features were added!
All information can be found in the updated description at top!
Stay tuned!

What's multithreading option?

saiojitsu said:
What's multithreading option?
Click to expand...
Click to collapse
each light zone should use its own CPU thread
https://blueforcer.de/jeelight-guide-and-faq/

Version 2.25 is online
new special “Twinkle”
Added a Tray Icon to control JeeLight while the Window is closed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Updated to latest Java Runtime

Any thoughts about adding a music mode that reacts to the beats in the song playing on the computer?

Nice program!
I've just tried Yeelight Toolbox, JeeLight and Androids Yeelight Music app. But there were some problems with JeeLight i think:
- Autodiscovery doesn't work. No bulbs were found. So i added them manualy with the IP adresses.
- The color change in the tab "playground" sometimes show's no effect. Sometimes it works, sometimes it wont.
But now the weird part:
After adding the bulbs in JeeLight, Yeelight Toolbox says on opening:
"Ungültige Länge für Base-64-Zeichenarray oder -Zeichenfolge" (Translated: "invalid length for a base-64 char array or string"). If i look into the Yeelight Music App, the names of my bulbs are broken. There are now something like
"G?/
or
"G?G
The current logfile of JeeLight:
Code:
windows 10
2.25
Waiting for Light 1
Light 1 connected!
set Musicmode for 1 to true
Waiting for Light 2
Light 2 connected!
set Musicmode for 2 to true
Waiting for Light 3
Light 3 connected!
set Musicmode for 3 to true
Waiting for Light 4
Light 4 connected!
set Musicmode for 4 to true
Waiting for Light 5
Light 5 connected!
set Musicmode for 5 to true
Waiting for Light 6
Light 6 connected!
set Musicmode for 6 to true
Ambilight started
Start Thread 1
Start Thread 2
Start Thread 3
Start Thread 4
Start Thread 5
Start Thread 6
(RuntimeException) java.lang.RuntimeException: Object should first be initialized (B4XBitmap).
Thread 2 started
Thread 1 started
My Windows 10 PC is connected via LAN.

Hi , i'm noob , i have this error on windows 10 , i install jdk-8u191-windows-x64
Failed to find library.
---------------------------
C:\Program Files\JeeLight\runtime\bin\server\jvm.dll
---------------------------
JeeLight.exe
---------------------------
Failed to locate JNI_CreateJavaVM
---------------------------
JeeLight.exe
---------------------------
Failed to launch JVM
any help please.

Blueray88 said:
Version 2.25 is online
new special “Twinkle”
Added a Tray Icon to control JeeLight while the Window is closed
Updated to latest Java Runtime
Click to expand...
Click to collapse
i m using Mac OS and wanted to try the app.. But the app can't find my devices (1st gen. Yeelight YLDP02YL RGBW)
(i do connect to internet with cable)
What may be wrong?