for all have dreambox and run Oscam this apps is oscam monitor tested on x10 mini and work after install in seting just add IP of your dreaMBOX and port you have set it for your web interface user and pass wrd save and clic conect ENJOY
Rev. 110
Connection error fixed, some nice new graphics added
change log
Rev.108
- Some improvement on status bar, avoid double request startup, support readonly attribute in XMLAPI header (controls disabled in controlpage)
THIS files is from sattelite dev's not dev by me i am dreambox firmewar devs i test this plugins on my IMG and work fine
Hi,
many thanks for this App, it is realy great! But, on a Samsung Galaxy S3 (ICS 4.1.2) mini I'm getting the following error message:
Unexpected token (Postition: TEXT access denied)
@2:1 in [email protected]
On my Xperia Sola (ICS 4.1.2) the App is running flawlessly.
Any idea what the problem could be?
Many thanks in advance!
gonzo
Hi,
it monitors oscam very good, only version is old - now on Android 10 (11)
It would be finde if it could be written into new app
useable now. (settings must be fit at first time open App - menü cannot open afterwards)
I wish it could give an app which is like openwebif in Browser. Nowhere to find.. only IOS has apps
Thanks
CM11 for WAVE and WAVE 2
Android Kitkat 4.4.2
Hi All,
So once again it’s time to upgrade our project to Android 4.4.2
Previous versions:
CM10: http://forum.xda-developers.com/showthread.php?t=1851818
CM10.1: http://forum.xda-developers.com/showthread.php?t=2400126
CM10.2: http://forum.xda-developers.com/showthread.php?t=2550138
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FEATURES
Android 4.4.2
CM sources of 13.01.2014
Updated to linux kernel version 3.0.101
270 MB RAM
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- Conference Calls
- Some problems with audio codec settings, but generally it should
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad.
You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-11.0 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-11.0/local_manifest.xml
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
cd .repo
wget https://raw.github.com/Badadroid/android_wave_local_manifest/cm-11.0/local_manifest.xml
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM from CHANGELOG section
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition or SD Card.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- "install zip"
- "choose zip from from storage/sdcard1"(Bada's User partition) or "choose zip from storage/sdcard0"(SD Card)
- cm-11-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS: http://d-h.st/users/ZordanKV/?fld_id=28623#files
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
CHANGELOG:
v4.4 http://www.multiupload.nl/SX2RTH51BC
- CM sources 2.06.2014
- Patches from SGS
v4.3 http://www.multiupload.nl/QS4A17BXXW
- CM sources 30.03.2014
- Many changes from CM core team
- Kernel with new optimization (Last Mackay Kernel from Nameless ROM)(new Zram algorithm, GPU fixes and etc. )
- Included fix for Wave2 from chemosun. This patch reduce Wave 2 screen wake up bug, i don't know about battery drain. He sent me it several months ago, but i forgot to include it to previous release
- Screen Frame rate path. Thanks to Alberto96
- Disabled 720p recording/playback. Big thanks to Alberto96 for idea and sources. It gave us more RAM.(total available in ROM 283MB) It is correctly disabled in ROM. so Photo camera is fully working, video camera is only 480p. For 720p playback you can use third-party apps like MXPlayer and etc.
If you go from previous releases, you need to clean data for Gallery and Camera application
v4.2 http://www.multiupload.nl/ZGB2Z5YOWD
- CM sources 21.02.2014
- Many changes from CM core team
-Added Basic GPS
v4.1.1 http://www.multiupload.nl/B7M535UJXH
- CM Sources 01.02.2014
- Zram 120Mb by default
- Some improvements for bootanimation
- Fixed some mistake in init, which can be the reason of some wi-fi problems
v4.1 http://www.multiupload.nl/5L9CCWZ4XA
- CM sources 28.01.2014
- Many changes from CM core team: Call delay workaround by pawitp was merged to CM sources, so no need to flash it
- Added test Battery thread to RIL https://github.com/Badadroid/androi...mmit/65d8d549e52761a9b8b673a0620c108773cf9ffd
- Added overlay for hardware camera key
v4 Initial CM11 release: http://www.multiupload.nl/YHC2P74SJZ
- CM Sources 13.01.2014
- Big patch set from mackay kernel http://forum.xda-developers.com/showthread.php?t=2532813 :
updated CPU governors, I/O schedulers, and many other performance patches
- 80Mb zRAM
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
question
thanks for update
this cm11 is running dalvik or art?
black0000 said:
thanks for update
this cm11 is running dalvik or art?
Click to expand...
Click to collapse
Dalvik is default Android Runtime for all kitkat ROMs.
Art is experimental feature from Google and still is WIP:
You can read more here:
http://source.android.com/devices/tech/dalvik/art.html
CM officially don't support Art, though it is possible to switch to Art in developer options
volk204 said:
Dalvik is default Android Runtime for all kitkat ROMs.
Art is experimental feature from Google and still is WIP:
You can read more here:
http://source.android.com/devices/tech/dalvik/art.html
CM officially don't support Art, though it is possible to switch to Art in developer options
Click to expand...
Click to collapse
according to you which one is better dalvik or art gor our wave
black0000 said:
according to you which one is better dalvik or art gor our wave
Click to expand...
Click to collapse
I didn't try Art, i can say that after last optimization changes performance is good enough even with dalvik.
@hero355, what you can say about performance of this ROM after playing Asphalt 7 on it?
volk204 said:
I didn't try Art, i can say that after last optimization changes performance is good enough even with dalvik.
@hero355, what you can say about performance of this ROM after playing Asphalt 7 on it?
Click to expand...
Click to collapse
Firstly I want to say big that's to volk204 for his great work
This time really it's a big step in badadroid development.
I've tested several kernel and I can say The phone is simply flying,The performance and optimization is perfect and we got now almost stable for 4 years old Samsung Wave phones
Secondly I've tested game performance and my tests was on Asphalt 7, (I haven't time for test other games- I'm not a gamer )
As you know there are some kernels with bigmem and zram .
I've tested all kernels with asphalt 7 and while all my tests I used 100~1000 MHz with interactive governor and game was running perfect
The best game performance was zram 120 with 1000mhz, I don't even imagine that with bigmem zram120 + 1400mhz it'll fly
So I can say now time to revert android to default
Thanks again volk204 and all badadroid developers
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Stevethegreat said:
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Click to expand...
Click to collapse
AFAIK camera is not working at all and photo also on Bigmem, added to OP, but i really don't see anysense to use bigmem, because in normal mode all is OK))
volk204 said:
AFAIK camera is not working at all and photo also on Bigmem, added to OP, but i really don't see anysense to use bigmem, because in normal mode all is OK))
Click to expand...
Click to collapse
Hey, nice work as always! But any chance of NAND version for this ROM?
Or can we use without bada n Tigrouzens Fota?
Stevethegreat said:
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Click to expand...
Click to collapse
No, camera app will not work, so no photos and video capturing.
sadiq23 said:
Hey, nice work as always! But any chance of NAND version for this ROM?
Or can we use without bada n Tigrouzens Fota?
Click to expand...
Click to collapse
No correct charger - No NAND version
volk204 said:
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/show...&postcount=393
Click to expand...
Click to collapse
The Link is not functional anymore. Shows that the forum specified is invalid.
Sandeep Srikantam said:
The Link is not functional anymore. Shows that the forum specified is invalid.
Click to expand...
Click to collapse
fixed
GAPPs
volk204 said:
fixed
Click to expand...
Click to collapse
There are two files in Slim GAPPs, test(newer) and an older version. Which one to download ?
Is this version noticeably faster than the previous one (3.1)?
WiFi Not Working
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
WaveII_Jil said:
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
Click to expand...
Click to collapse
Search for Wifi fix zip , I don't know where is ,I think in 3.1 or 2.1 thread
WaveII_Jil said:
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
Click to expand...
Click to collapse
anyone with wave2 has the same problem?
Did you do clean installation with removing previous version of android and installing new version or just flashed zip via recovery?
No logs - no problems
florynwk3 said:
Search for Wifi fix zip , I don't know where is ,I think in 3.1 or 2.1 thread
Click to expand...
Click to collapse
It is useless
volk204 said:
anyone with wave2 has the same problem?
Did you do clean installation with removing previous version of android and installing new version or just flashed zip via recovery?
No logs - no problems
Click to expand...
Click to collapse
I did a clean installation by uninstalling previous version and installing new version. Sorry, could not get the logs.
Just wanted to know if this issue exists only in my phone or others also...
BUG: encrypt device ...
hi folks,
great work volk thats really exciting..
the interesting lines are:
ActivityManager( 503): Resuming delayed broadcast
I/ActivityManager( 1035): Timeline: Activity_launch_request id:com.android.settings time:3037005
I/ActivityManager( 503): START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from pid 1035
D/PhoneStatusBar( 658): disable: < EXPAND* ICONS* ALERTS* ticker SYSTEM_INFO* BACK* HOME* RECENT* clock SEARCH* >
I/ActivityManager( 503): Displayed com.android.settings/.CryptKeeperConfirm$Blank: +359ms
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3037409
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41d115a0 u0 com.android.settings/.CryptKeeperConfirm$Blank t4} time:3037702
E/Cryptfs ( 156): Cannot get size of block device
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3047091
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41ca10d0 u0 com.android.settings/.SubSettings t4} time:3047384
D/Tethering( 503): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
I/ActivityManager( 1035): Timeline: Activity_launch_request id:com.android.settings time:3051736
I/ActivityManager( 503): START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from pid 1035
I/ActivityManager( 503): Displayed com.android.settings/.CryptKeeperConfirm$Blank: +103ms
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3051879
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41cbcb58 u0 com.android.settings/.CryptKeeperConfirm$Blank t4} time:3052206
E/Cryptfs ( 156): Cannot get size of block device
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3060969
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41ca10d0 u0 com.android.settings/.SubSettings t4} time:3061295
I think
E/Cryptfs ( 156): Cannot get size of block device
is the line to be interpreted...
Can someone please have a look into it...
logcat & co are attached
Hi all,
I need help testing our app on LG L5 II (E450) running Android 4.1.2. It seems that other LG devices running 4.1.2 would have the same issue.
So if someone is running 4.1.2 on an LG device, I would ask you to install the first attached APK, try to crash the app. Then install the 2nd APK and confirm that (hopefull!) it doesn't crash anymore...
I've attached 2 APK builds here. The first build is the same as the one on the playstore
https://play.google.com/store/apps/details?id=com.muzooka.player
Reading various threads leads me to 2 possible reasons:
Using a custom font (SpannableString) for the ActionBar title
Missing `android:titleCondensed` when creating ActiobBar menu item
If I understood this right, then here are the steps to crash the app:
If it's the first reason, then the app should crash right away
If it's the second one, then the app should crash when accessing the actiobar overflow menu. Steps to crash:
Open app and go throught the welcome screens
on the first screen, select *Charts* from the left navigation drawer
On the Charts, tap a song's menu (vertical dots) and go to *Artist info*
Long press on the share icon (to display the description tip box), or do a search.
Crashed?
If both tests don't crash the app, feel free to click around trying to crash it.
The Crashlytics bug report
http://crashes.to/s/fad5f37453f
The raw log:
Code:
java.lang.IllegalArgumentException: Invalid payload item type
at android.util.EventLog.writeEvent(EventLog.java)
at android.app.Activity.onMenuItemSelected(Activity.java:2766)
at android.support.v4.app.FragmentActivity.onMenuItemSelected(FragmentActivity.java:373)
at android.support.v7.app.ActionBarActivity.superOnMenuItemSelected(ActionBarActivity.java:245)
at android.support.v7.app.ActionBarActivityDelegateICS.onMenuItemSelected(ActionBarActivityDelegateICS.java:164)
at android.support.v7.app.ActionBarActivity.onMenuItemSelected(ActionBarActivity.java:131)
at android.support.v7.app.ActionBarActivityDelegateICS$WindowCallbackWrapper.onMenuItemSelected(ActionBarActivityDelegateICS.java:308)
at com.android.internal.widget.ActionBarView$3.onClick(ActionBarView.java:172)
at android.view.View.performClick(View.java:4101)
at android.view.View$PerformClick.run(View.java:17088)
at android.os.Handler.handleCallback(Handler.java:615)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:153)
at android.app.ActivityThread.main(ActivityThread.java:5071)
at java.lang.reflect.Method.invokeNative(Method.java)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
at dalvik.system.NativeStart.main(NativeStart.java)
Related to following threads:
* https://code.google.com/p/android/issues/detail?id=58723
* http://stackoverflow.com/questions/...alargumentexception-invalid-payload-item-type
* http://stackoverflow.com/questions/21807298/invalid-payload-type-android
Hi, i am new, and i hope to write in the right section.
I follow the guide about installation of Xpsoed Addition. Everything seems going good, but when i open Xpsoed Additions there is an error:
"Missing System Service. The Xposed additions system service is currently not enabled. If you have just updated this module, please reboot the device to activate it. Otherwise, make sure that XposedBridge is installed and that this module is enabled."
When i open Exposed Framework if i go to framework section i can see: app_process active 58 (in green), last 58 (in grey); XpsoedBridge.jar active 54 (in green), last 54 (in grey). The module is active and i have reboot he device. I installed it trought the Xposed installer download section. I have an acer liquid E2 duo with android 4.2.2 rooted. How can i fix this error?
Same Here
ScTALE said:
Hi, i am new, and i hope to write in the right section.
I follow the guide about installation of Xpsoed Addition. Everything seems going good, but when i open Xpsoed Additions there is an error:
"Missing System Service. The Xposed additions system service is currently not enabled. If you have just updated this module, please reboot the device to activate it. Otherwise, make sure that XposedBridge is installed and that this module is enabled."
When i open Exposed Framework if i go to framework section i can see: app_process active 58 (in green), last 58 (in grey); XpsoedBridge.jar active 54 (in green), last 54 (in grey). The module is active and i have reboot he device. I installed it trought the Xposed installer download section. I have an acer liquid E2 duo with android 4.2.2 rooted. How can i fix this error?
Click to expand...
Click to collapse
I am having the same issue with the amazon fire phone, rooted on CM 11, anybody able to help ?