acDeskClock
{
"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"
}
Support:
- Android 4.0+
Features:
- All CM9/ICS's features
- Reworked Alarm's UI
- Shake device to stop/snooze/nothing alarm
- Are you awake? - Solve a math quiz to stop the Alarm
- Increasing volume
- Stopwatch
Sources:
- Available on GitHub *updated 21.06.12*
Thanks:
- Android / CyanogenMod teams
Post Scriptum:
- If you want to use acDeskClock in your fantastic ROM - don't forget to ask me.
CM7 acDeskClock
Support:
- Android 2.3+
Features:
- All CM7/GB's features
- Fixed themes support
- Shake device to stop/snooze/nothing alarm
- Flip down device to stop/snooze/nothing alarm
- Are you awake? - Solve a math quiz to stop the Alarm
- Increasing volume
Sources:
- Available on GitHub
Thanks:
- Android / CyanogenMod teams
Post Scriptum:
- If you want use acDeskClock in your fantastic ROM - don't forget to ask me.
The Alarm Man strikes!
amazing D:
Thanks bro.
AChep, i have CM7 DeskClock force close (tried on MiniCM 2.2.1 @ nAa11).
mr-tical said:
AChep, i have CM7 DeskClock force close (tried on MiniCM 2.2.1 @ nAa11).
Click to expand...
Click to collapse
Try to redownload and flash .zip again. If still FC - logcat
AChep said:
Try to redownload and flash .zip again. If still FC - logcat
Click to expand...
Click to collapse
See attachments.
Second txt is on default MiniCM theme.
edit
Found this, can be?
"Can't find com.google.android.apps.genie.geniewidget"
I've deleted this app form rom, don't need.
nice one achep,btw can you add stopwatch and timer to the deskclock app,it would be gr8
Very efficient oO*
ihsan123 said:
nice one achep,btw can you add stopwatch and timer to the deskclock app,it would be gr8
Click to expand...
Click to collapse
Stopwatch and timer, that would be great!
Basic tools under hand.
mr-tical said:
Stopwatch and timer, that would be great!
Basic tools under hand.
Click to expand...
Click to collapse
i can
AChep said:
i can
Click to expand...
Click to collapse
Did You see my logs?
AChep said:
Try to redownload and flash .zip again. If still FC - logcat
Click to expand...
Click to collapse
I Had the same problem,but i solved it uninstalling the stock deskclock.apk and then flash your .zip and now i have no problems!
Great work by the way!
RodrigoOgasawara said:
I Had the same problem,but i solved it uninstalling the stock deskclock.apk and then flash your .zip and now i have no problems!
Great work by the way!
Click to expand...
Click to collapse
Thanks for tip
MiniCM is odexed, so i've deleted DeskClock.odex more and it work.
Well AChep your apk is in conflict with odex file.
I am trying to build Aokp and I wanted to add your clock in it! I used the source code on your github but I get this error on compiling!
Code:
target R.java/Manifest.java: DeskClock (out/target/common/obj/APPS/DeskClock_intermediates/src/R.stamp)
Warning: AndroidManifest.xml already defines versionCode (in http://schemas.android.com/apk/res/android); using existing value in manifest.
Warning: AndroidManifest.xml already defines versionName (in http://schemas.android.com/apk/res/android); using existing value in manifest.
packages/apps/DeskClock/res/layout/alarm_math.xml:24: error: Error: This attribute must be localized. (at 'text' with value '1').
packages/apps/DeskClock/res/layout/alarm_math.xml:31: error: Error: This attribute must be localized. (at 'text' with value '2').
packages/apps/DeskClock/res/layout/alarm_math.xml:38: error: Error: This attribute must be localized. (at 'text' with value '3').
packages/apps/DeskClock/res/layout/alarm_math.xml:52: error: Error: This attribute must be localized. (at 'text' with value '4').
packages/apps/DeskClock/res/layout/alarm_math.xml:59: error: Error: This attribute must be localized. (at 'text' with value '5').
packages/apps/DeskClock/res/layout/alarm_math.xml:66: error: Error: This attribute must be localized. (at 'text' with value '6').
packages/apps/DeskClock/res/layout/alarm_math.xml:80: error: Error: This attribute must be localized. (at 'text' with value '7').
packages/apps/DeskClock/res/layout/alarm_math.xml:87: error: Error: This attribute must be localized. (at 'text' with value '8').
packages/apps/DeskClock/res/layout/alarm_math.xml:94: error: Error: This attribute must be localized. (at 'text' with value '9').
packages/apps/DeskClock/res/layout/alarm_math.xml:108: error: Error: This attribute must be localized. (at 'text' with value '0').
packages/apps/DeskClock/res/layout/alarm_math.xml:115: error: Error: This attribute must be localized. (at 'text' with value '←').
make: *** [out/target/common/obj/APPS/DeskClock_intermediates/src/R.stamp] Error 1
stelios97, today i deleted repo. Wait for some time while i recovering it.
AChep said:
stelios97, today i deleted repo. Wait for some time while i recovering it.
Click to expand...
Click to collapse
Ok! I fixed the error by changing some values on the xmls and makefile!
stelios97 said:
Ok! I fixed the error by changing some values on the xmls and makefile!
Click to expand...
Click to collapse
btw you forgot to ask me about something
Related
For chefs ONLY !
Thats the reason I put it here, if that's wrong, please tell me and move to the correct forum.
ROMAbout
{
"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"
}
This neat little app/package is intended to include in your ROM while building.
It will enable you to add important information about your ROM and credits.
It consists of a XAP, a Data folder with information and images and also an rgu that you have to customize for your particular ROM.
More information about the customization in the next posts.
Changelog
1.0.0.0 - 2012-03-30
- First public release.
1.1.0.0 - 2012-04-22
- Selected values are editable through list, text or slider.
Features I'm working on
- Letting the cooker add their own PanoramaItems by defining them in the ROMData.xml
Preparing for use in ROM !
Here you'll find information about how to prepare the XAP and the other files for your ROM.
The XAP contains a folder named Data that contains the ROMData.xml and images that are connected to the different entries in the ROMData.xml. More information about how to edit the ROMData.xml in the next post.
Edit the ROMData.xml and the RGU, and add some images (if used) to the Data folder in the XAP.
When you've edited the XAP and the RGU you HAVE to update the DSM so it reflects the changes. I recommend you to use OsBuilder by Barin and Ultrashot to do this.
Now the package is ready to be included in your ROM
ROMData.xml
Information about the ROMData.xml file and what you're able to do with it.
The ROMData.xml contains all information and/or registry paths to the information shown in the app.
The BEST way to get to understand this is by looking at the original ROMData.xml supplied in the unmodified XAP.
It is also attached to this post if you don't have the original.
To edit the description shown in the settingslist you change the <description> element. It could also be a registry path, preferably to a value defined in the RGU. As an example:
<description>{HKLM\RomAbout\Description}</description>
And here's the syntax for an item element:
<item image="[/Data/[NAME_OF_IMAGE]]" title="[NAME_OR_REGISTRY_PATH]" info="[TEXT_OR_REGISTRY_PATH]" other="[TEXT_OR_REGISTRY_PATH]" editable="[false/list/text/slider]" reqreboot="[true/false]" />
An example of an item without options could be something like this:
<item image="/Data/defIcon.jpg" title="{HKLM\System\Platform\DeviceTargetingInfo\OemDeviceName}" info="The OEM name of this device" other="{HKLM\System\Platform\DeviceTargetingInfo\OemName}" editable="false" reqreboot="false" />
An example of an item with options could be something like this:
<item image="/Data/defIcon.jpg" title="{HKLM\System\Platform\DeviceTargetingInfo\OemDeviceName}" info="The OEM name of this device" other="{HKLM\System\Platform\DeviceTargetingInfo\OemName}" editable="text" reqreboot="false">
<option title="Please enter your desired OEM name" path="HKLM\System\Platform\DeviceTargetingInfo\OemName" description="The OEM name affects which OEM market you can access, f.ex HTC gives you access to HTC's market" value="HTC"/>
</item>
When using a registry path, the hive is ALWAYS shortened down !
HKEY_LOCAL_MACHINE = HKLM
HKEY_CURRENT_USER = HKCU
HKEY_CLASSES_ROOT = HKCR
HKEY_USERS = HKU
The RGU
Information about the RGU included in the package.
The RGU contains some registry values that you could use in the ROMData.xml.
You really should edit these values and maybe add some of your own.
The examples are all stored in HKLM\RomAbout but you could specify your own path, just make sure you use the same paths in ROMData.xml.
The default values in the RGU are just examples. You could name them to whatever you want, just point to them in the ROMData.xml.
Credits & Download
Credits
Heathcliff for his awesome SDK that solved the last things for me
Downloads
Here is the link to the XAP - https://www.dropbox.com/s/zfl772t6ymiryxf/ROMAbout.xap
And here is for the package with the registry entries - https://www.dropbox.com/sh/m0m8wetyxz0iwvs/Qn5qeiMhpq
v1.0.0.0 - 2012-03-30
v1.1.0.0 - 2012-04-22
Nice work man this is very useful!
my next rom will have this , thanks man really love it
ceesheim said:
my next rom will have this , thanks man really love it
Click to expand...
Click to collapse
There will soon be an update (that won't require updated files if you won't use the new features) that allows the user to edit values, either by manually inputting a string or selecting a value from a listbox. That's up to the cooker
Just have a bit of a problem with the XML parsing for some reason
Cool app... will include in the next release of my custom Rom. Thanks man.
Thanks
any news about Version 2 with easier info editing?
nice work
It's going good, but it could take about a week to have the options thing working I guess. Got some minor issues with it at the moment.
Regards
Izaac
Done some progress with the editing. Will probably upload a new version soon that enables editing values by selecting from list, entering text or from a slider for the numeric values. Already done with the list options, and almost done with the text also.
Regards
Izaac
IzaacJ said:
Done some progress with the editing. Will probably upload a new version soon that enables editing values by selecting from list, entering text or from a slider for the numeric values. Already done with the list options, and almost done with the text also.
Regards
Izaac
Click to expand...
Click to collapse
Thanks
looking forward for it...keep up the good work
Just uploaded the new version and edited all the posts
I'm feeling a bit done with this project as it fullfills my personal needs, but I will keep on doing some work and improvements on it.
Feel free to ask for new features that I could implement.
I'd love to add a list with ROMs that features this app to the first post, so please either post or PM me a link to your thread and I'll link it here
EDIT: I'm going to update it for WP 7.8 and add LiveTiles support, for small, medium and large tiles. What information would you guys like to see on the tiles?
Regards
Izaac
{
"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"
}
Info
I bring to you, a Xperia Z theme for CM (various editions). Tho I havent tested this as I moved on from my Pro, but it looks great on my Note ll. It comes complete with everything from basic scrubbers to app themes. Please HDPI users provide me with screenshots. Not totally my work, merge. Here's a list of the Xperia Z themed system:
Phone
Contacts
Trebuchet
Messaging
Camera
Apollo
Calender
Calculator
Icons
Settings
Gallery
SystemUI
Framework
Download
Click here to Download Version 1.01
Changelog
Build 12/02/13
-Initial release
-Z themed
Screenshots
Please provide them
it says app not installed
AW: [Theme Chooser][CM+] Xperia Z UI | Delivered
Where are the screenshots??
sorry for my little english
XtremeSilencer said:
it says app not installed
Click to expand...
Click to collapse
+1
Hotfingers said:
+1
Click to expand...
Click to collapse
?! Logcat please? When installing app.
Screenshot!!!
It's X-Ray with Tapatalk!
frogerra said:
Screenshot!!!
It's X-Ray with Tapatalk!
Click to expand...
Click to collapse
cant you read the first post???
Gonna try rebuilding the app today. Lets hope that installs
I hope this one helps
I am on stock rom
Code:
W/ActivityManager(977): finishReceiver called but no pending broadcasts
E/ProcessKiller(164): Process sh (6021) has cwd within /mnt/secure/staging
E/ProcessKiller(164): Process com.android.defcontainer (6322) has open file /mnt/secure/staging/Bluetooth/XperiaZUI_1.0.apk
E/ProcessKiller(164): Process com.android.packageinstaller (8099) has open file /mnt/secure/staging/Bluetooth/XperiaZUI_1.0.apk
W/Vold (164): Failed to unmount /mnt/secure/staging (Device or resource busy, retries 8, action 0)
E/ProcessKiller(164): Process sh (6021) has cwd within /mnt/secure/staging
E/ProcessKiller(164): Process com.android.defcontainer (6322) has open file /mnt/secure/staging/Bluetooth/XperiaZUI_1.0.apk
E/ProcessKiller(164): Process com.android.packageinstaller (8099) has open file /mnt/secure/staging/Bluetooth/XperiaZUI_1.0.apk
W/ResourceType(977): getEntry failing because entryIndex 1333 is beyond type entryCount 115
W/ResourceType(977): Failure getting entry for 0x02020535 (t=1 e=1333) in package 0 (error -2147483647)
W/ActivityManager(977): No content provider found for permission revoke: file:///mnt/sdcard/bluetooth/XperiaZUI_1.0.apk
W/PackageParser(977): Unknown element under <manifest>: theme at /data/app/vmdl1607780795.tmp Binary XML file line #6
D/dalvikvm(977): GC_FOR_ALLOC freed 691K, 37% free 14501K/22919K, paused 558ms
W/ActivityManager(977): finishReceiver called but no pending broadcasts
D/dalvikvm(977): GC_CONCURRENT freed 1139K, 35% free 15012K/22919K, paused 2ms+8ms
W/Vold (164): Failed to unmount /mnt/secure/staging (Device or resource busy, retries 7, action 0)
E/ProcessKiller(164): Process sh (6021) has cwd within /mnt/secure/staging
I/ActivityManager(977): Start proc com.sonyericsson.android.socialphonebook for service com.sonyericsson.android.socialphonebook/.smartsearch.SmartSearchCachingService: pid=8160 uid=10015 gids={3003, 1015}
E/ProcessKiller(164): Process com.android.packageinstaller (8099) has open file /mnt/secure/staging/Bluetooth/XperiaZUI_1.0.apk
D/dalvikvm(977): GC_CONCURRENT freed 784K, 31% free 15969K/22919K, paused 16ms+6ms
D/dalvikvm(8160): GC_CONCURRENT freed 164K, 3% free 7905K/8135K, paused 4ms+2ms
W/socialphonebook(8160): SettingsParser: text is nothing.
W/Vold (164): Failed to unmount /mnt/secure/staging (Device or resource busy, retries 6, action 0)
D/CustomizationProvider(1154): openFile -- START uri=content://com.sonyericsson.provider.customization/settings/com.sonyericsson.android.socialphonebook
I/CustomizationProvider(1154): No configuration file: /system/etc/customization/settings/com/sonyericsson/android/socialphonebook/custom_settings.xml
W/socialphonebook(8160): SettingsParser: No customization file exists.
E/socialphonebook(8160): SettingsParser: key not found. key=[account-types]
D/AccountTypeManager(8160): Registering 1 extension packages
I/AccountTypeManager(8160): Loaded meta-data for 3 account types, 1 accounts in 41ms(wall) 8ms(cpu)
E/ProcessKiller(164): Process sh (6021) has cwd within /mnt/secure/staging
E/ProcessKiller(164): Process com.android.packageinstaller (8099) has open file /mnt/secure/staging/Bluetooth/XperiaZUI_1.0.apk
W/PackageParser(977): Exception reading AndroidManifest.xml in /data/app/vmdl1607780795.tmp
W/PackageParser(977): java.lang.SecurityException: META-INF/MANIFEST.MF has invalid digest for AndroidManifest.xml in /data/app/vmdl1607780795.tmp
W/PackageParser(977): at java.util.jar.JarVerifier.invalidDigest(JarVerifier.java:131)
W/PackageParser(977): at java.util.jar.JarVerifier.access$100(JarVerifier.java:53)
W/PackageParser(977): at java.util.jar.JarVerifier$VerifierEntry.verify(JarVerifier.java:123)
W/PackageParser(977): at java.util.jar.JarFile$JarFileInputStream.read(JarFile.java:119)
W/PackageParser(977): at java.io.BufferedInputStream.read(BufferedInputStream.java:304)
Odp: [Theme Chooser][CM+] Xperia Z UI | Delivered
am2222 said:
I hope this one helps
I am on stock rom
Click to expand...
Click to collapse
It's only for CM...
Sent from my LT22i using xda-developers app
Is it working now??
Sent from my Xperia Ray using xda app-developers app
dark ryder said:
Is it working now??
Sent from my Xperia Ray using xda app-developers app
Click to expand...
Click to collapse
It is not working for official CM10 for me.
OP updated with new link. Let me know if that works
emwno said:
OP updated with new link. Let me know if that works
Click to expand...
Click to collapse
It's Alive!, looks great, working on FXP CM10 207.
Yes, it works very good
here some Screens
WORKING OK ON JB 4.2 (MK16)
I was using Nova, and only had that Xperia wallpaper. the only bug I found was a misaligned PNG, below the carrier name (TELCEL in my phone)
deleted
it works great actually, didn't know i have to apply via theme
thanks, great work
Sent from my Xperia Arc S using xda app-developers app
Works on Super Jelly Bean 2.0, thanks! Is it possible to add battery percentage next to the icon?
Guys please don't download, it is thomassafca's xperia theme cracked with another package name. Mods please remove thread
Sent from my Xperia Ray using xda app-developers app
Thats what everyone says. Its a merge of a base with the xperia z framework. The pngs are the same. They cabt be changed now can they?
{
"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"
}
What is Chameleon OS:
Chameleon OS (or ChaOS for short) is a custom Android ROM that gives the user more control than they can experience on any other Android ROM. Starting with a CyanogenMOD base, we customize each piece to give ultimate control while maintaining the simplicity we all love about Android. The most notable feature of ChaOS is the theme engine, which can apply different pieces of themes in a true mix-and-match style. The launcher has been completely overhauled with tons of options that you'd normally need to download a third-party launcher for, such as home screen previews, folder sorting, and folder icon styles. The Messaging app has also had some UI retouches, including messaging bubbles and quick emoji button.
The entire framework of ChaOS has been modified around the theme engine, allowing for custom fonts, boot animations (with animated preview), and themes. No longer do you have to try to find the perfect theme, with Chameleon OS you can patch it together with your favorite pieces from different themes. Messaging, Phone, Status Bar, icons, everything can be set completely individually from each other which provides the capabilities to completely re-imagine your phone. Creating themes for the ChaOS Theme Engine is superbly simple and has extreme versatility.
Even with all of the features we've currently implemented, ChaOS will continue to mature with even more refined settings and features. We will be completely open source and will welcome developers to join us, whether it be by maintaining a device or utilizing our gerrit review. Even if you're not a developer, your voice will not go unheard. We will continually poll our users for the most wanted features and do our best to implement them.
Features of ChameleonOS:
Built on CM so basic CM features are included
Fully open source, contribute features and fix bugs
Launcher Features
Folder icon styles: stacked, grid, or carousel
Folder sorting: alphabetically, reverse alphabetically, or by usage
Icon scaling in app drawer and on homescreen
Home screen previews, rearrangable homescreens
Set default screen from previews layout
Add or remove homescreens from previews layout
Slide homescreens with a second finger while holding widgets and icons
Customizable gestures: slide up, slide down, pinch, and spread
Theme Manager
Based on MIUI's theme engine
Mix and match different themes on the fly
Theme options: Icons, Status Bar, Boot animation, Font (requires reboot), Messaging, Framework, and Ringtones
Applies native ctz files, but also will apply MIUI mtz files, not all elements will theme properly with mtz packages
Animated boot animation preview
Boot animation resolution scaling
Status Bar
Customizable toggles, compact or page view (or off)
Extended volume panel in page view toggles
Access status or navigation bars while in fullscreen apps by touching the edge of the screen
Messaging
Reads custom notification tones from Contacts
Revised layout: Added messaging bubbles, removed avatar icons from conversation and put one in the action bar, quick shortcut for emojis
Security
Manage installed apps' permissions
Donwloads:
First preview version:
XDA:DevDB Information
Chameleon OS , a ROM for the Sony Xperia Sola
Contributors
werty100, Diego910, Gava97, munjeni Maclaw DroidModderXtreme all people on xda helping us
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: First
Beta Release Date: 2013-11-30
Created 2013-11-30
Last Updated 2013-11-30
Boys i am having problems in,compilation so i need help of the good devemlpers
Enviado desde mi Xperia U mediante Tapatalk
Error?
DroidModderXtreme said:
Error?
Click to expand...
Click to collapse
Recovery:
mport includes file: /media/android/Chamaleon/out/target/product/kumquat/obj/EXECUTABLES/recovery_intermediates/import_includes
target thumb C: recovery <= bootable/recovery/recovery.c
target thumb C: recovery <= bootable/recovery/bootloader.c
target thumb C: recovery <= bootable/recovery/install.c
target thumb C: recovery <= bootable/recovery/roots.c
target thumb C: recovery <= bootable/recovery/ui.c
bootable/recovery/ui.c: In function 'update_leds':
bootable/recovery/ui.c:772:42: error: 'RED_LED_FILE' undeclared (first use in this function)
bootable/recovery/ui.c:772:42: note: each undeclared identifier is reported only once for each function it appears in
bootable/recovery/ui.c:773:42: error: 'GREEN_LED_FILE' undeclared (first use in this function)
bootable/recovery/ui.c: In function 'ui_rainbow_mode':
bootable/recovery/ui.c:1642:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
make: *** [/media/android/Chamaleon/out/target/product/kumquat/obj/EXECUTABLES/recovery_intermediates/ui.o] Error 1
Then i delete RED_LED_FILE and GREEN_LED_FILE strings
Then happen this:
leds_thread error
i have delete it now i have to build....
Now it its bulding it....
(I don't know this)
If Chameleon CWM Modified ?
If yes use cm's bootable recovery (add it inda manifest)
If not .... dont know :-\
DroidModderXtreme said:
(I don't know this)
If Chameleon CWM Modified ?
If yes use cm's bootable recovery (add it inda manifest)
If not .... dont know :-\
Click to expand...
Click to collapse
i will upload the device tre and manifiest with your help if it works the build....
werty100 said:
I think it is almost finnishing like 1 hour or 2 hours
Click to expand...
Click to collapse
target SharedLib: libwebviewchromium (/media/android/Chamaleon/out/target/product/kumquat/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so)
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/media/android/Chamaleon/out/target/product/kumquat/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
After all i get thsi error please @Gava97 @munjeni @DroidModderXtreme
werty100 said:
target SharedLib: libwebviewchromium (/media/android/Chamaleon/out/target/product/kumquat/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so)
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/media/android/Chamaleon/out/target/product/kumquat/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
After all i get thsi error please @Gava97 @munjeni @DroidModderXtreme
Click to expand...
Click to collapse
Triying to boot rom...
werty100 said:
Triying to boot rom...
Click to expand...
Click to collapse
not booting and no adb
use cm's chromium. . I think that is normal that you got lots of error coz chameleon 4.4 it's still not released
werty100 said:
not booting and no adb
Click to expand...
Click to collapse
Hey if the ROM isn't working just as yet, please do mention on the first page.As right now, it just mentions that it has bugs of CM11. Note which build of CM11 btw were u implying?
Because XDA DevDB isnt supported for XP and XU,just for XSola grrr...
werty100 said:
target SharedLib: libwebviewchromium (/media/android/Chamaleon/out/target/product/kumquat/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so)
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/media/android/Chamaleon/out/target/product/kumquat/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
After all i get thsi error please @Gava97 @munjeni @DroidModderXtreme
Click to expand...
Click to collapse
That error is because of low-memory. The free RAM in your machine is really less. You can try to use more swap.
Cheers,
AJ
Abhinav2 said:
That error is because of low-memory. The free RAM in your machine is really less. You can try to use more swap.
Cheers,
AJ
Click to expand...
Click to collapse
I got the same error sime time ago,just let the machine free without using other apps in background
No download so this thread is simply a placeholder which is not allowed on XDA.
In future, please don't create the thread before having everything ready including the download.
Once you have something available, press the report button and request the thread be reopened.
Until then, thread closed.
Here is a Xposed module, which port omni's splite view to other ROM.
Features:
*Support splite view and work with two workspace.
*Switch app into splite view in any situations.
*Could switch landscape and portrait.
*Support use SideBar to use.
*Sidebar Settings.
Note:
*Now,two workspace is perfect.
*MIUI user plaes allow floating window.
How to use(please install xposed before):
*FIRST,click the preference item to open the SideBar.
*THEN,you can slide from left to right and open SideBar window.
*AT LAST,you just set the SideBar window position and enjoy splite view.
Test:
*MIUI work fine.
*stock rom work fine.
Thanks to:
*@zst123(I based on his halo float window)
Change Log:
BETA-1.0.0:
*base usage.
*floting window control.
BETA-1.0.1:
*update display.
*support instruction.
BETA-1.0.2:
*fix landscape and portrait.
1.1.0
*fix sub activity'problem,close to perfect(all thanks to zst123)
*fix other devices' resolution.
*fix conflict with xhalo and omni and halo and samsung.(i change the flags that diffrent other).
1.5.0
*NEW:add SideBar and earily to use.
*clean code
1.6.0:
*NEW:Sidebar update and add Sidebar Settings
*code clean.
BUG List:
*some app not work(like fuubo and at present one)
**if exist two app,and one of them couldn't touch item.
Download page:
http://repo.xposed.info/module/com.lovewuchin.xposed.xmultiwindow
{
"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"
}
File:
1.6.0:
View attachment XMultiWindow.apk
No download link ? No picture preview ?
Sent from Bandung
Vuska said:
No download link ? No picture preview ?
Sent from Bandung
Click to expand...
Click to collapse
I am newer and uploading now
Take your time my friend cuz this is something we wait for it for ever.
Thank u so much
MR.Samo said:
Take your time my friend cuz this is something we wait for it for ever.
Thank u so much
Click to expand...
Click to collapse
but it also has some bugs and i coudn't solve it,i really hope some one can help me
Great work dev! Haha. I knew someone will create this!
I think you should say that this uses the same 0x2000 flag as Halo and will conflict with ROMs with halo.
Request to use 0x1000 (so it will not conflict and we will have best of both).
Can you upload your file here? The browser can't parse the address posted man.
Edit: already downloaded from repo now. Gonna try it later. Thanks OP.
happiness4u said:
Can you upload your file here? The browser can't parse the address posted man.
Edit: already downloaded from repo now. Gonna try it later. Thanks OP.
Click to expand...
Click to collapse
as you can see,i am a new and i could write links.
and i'll uplode file immediately.
zst123 said:
Great work dev! Haha. I knew someone will create this!
I think you should say that this uses the same 0x2000 flag as Halo and will conflict with ROMs with halo.
Request to use 0x1000 (so it will not conflict and we will have best of both).
Click to expand...
Click to collapse
i think i use a not good way to solve this problem because i use two flag with two view,and the two position will conflict,and the most problem is that the subactivity couldn't add to the pointing view,could you help me?
LovewuChin said:
i think i use a not good way to solve this problem because i use two flag with two view,and the two position will conflict,and the most problem is that the subactivity couldn't add to the pointing view,could you help me?
Click to expand...
Click to collapse
In your ActivityRecord class hook, you can use these to check. Then use taskAffinity (I refer to my source code)
Code:
boolean top_window = (i.getFlags() & 0x2000) == 0x2000;
boolean bottom_window = (i.getFlags() & 0x1000) == 0x1000;
....
....
if ( (top_window || bottom_window) && taskAffinity ) {
Field intentField = param.thisObject.getClass().getDeclaredField("intent");
intentField.setAccessible(true);
Intent newer = (Intent) intentField.get(param.thisObject);
if (top_window) {
newer.addFlags(0x2000);
}
if (bottom_window) {
newer.addFlags(0x1000);
}
intentField.set(param.thisObject, newer);
floatingWindow = true;
}
You can try this and see if it works.
(On a side note, do you speak chinese?)
zst123 said:
In your ActivityRecord class hook, you can use these to check. Then use taskAffinity (I refer to my source code)
Code:
boolean top_window = (i.getFlags() & 0x2000) == 0x2000;
boolean bottom_window = (i.getFlags() & 0x1000) == 0x1000;
....
....
if ( (top_window || bottom_window) && taskAffinity ) {
Field intentField = param.thisObject.getClass().getDeclaredField("intent");
intentField.setAccessible(true);
Intent newer = (Intent) intentField.get(param.thisObject);
if (top_window) {
newer.addFlags(0x2000);
}
if (bottom_window) {
newer.addFlags(0x1000);
}
intentField.set(param.thisObject, newer);
floatingWindow = true;
}
You can try this and see if it works.
(On a side note, do you speak chinese?)
Click to expand...
Click to collapse
yes,i speak chinese! and thank you for sloving my problem!
How can i close the floating blue circle?
Great idea but I think it need some work... Apps show above other apps... Alot of space under the down workspace and the navbar bar... And after that whatever app I open normally it shows on above workspace
Sent from my Nexus 5 using XDA Premium 4 mobile app
Simply amazing. Keep up dev:good:
very good, working perfectly on my galaxy s4-I9505 with android 4.3 stock
Well dev..does it conflict with xhalo floating window module?
Sent from my Micromax A110Q using XDA Premium 4 mobile app
great module, works good. Got a reboot while trying it but I can understand its just an initial release.
wow wow wow wow wow!!! thankssssss
Tried it in Tab 2 with 4.2.2 Stock and Touchwiz. App got confused and opened the launcher in half the screen and now everything is a mess Also it doesn't close all windows to restore everything when the option is chosen so I had to reboot Great work. Can't wait for the bugs to get ironed out
After touchwiz crashed and with the main homescreen loaded, I managed to open feedly and youtube together with no problem.
Good work. Please don't give up, all people want this !!!
So,
the G Pad (v500) comes with in two versions.
One version has the S5K4E5YA as back camera.
Other version hast the OV5693 as back camera.
As we know the S5K4E5YA already has support in AOSP and CM ROMs and kernels.
So I tried to add the missing files and references to the CM kernel.
https://github.com/drbeat/kernel_lge_v500/commit/7c9beb4a27fc65b60786616c5c966e53632dfc5d
These are changes I picked out from the "V50020D" kernel sources.
In compiling I get this error
Code:
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: error: extra brace group at end of initializer
{FALSE, 0, 0, 1},
^
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: error: (near initialization for ‘ov5693_calib_supp_info’)
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: warning: excess elements in struct initializer
drivers/media/video/msm/eeprom/ov5693_eeprom.c:68:2: warning: (near initialization for ‘ov5693_calib_supp_info’)
drivers/media/video/msm/eeprom/ov5693_eeprom.c:82:27: error: invalid application of ‘sizeof’ to incomplete type ‘struct msm_calib_id’
{&ov5693_id_data, sizeof(struct msm_calib_id)}, /* */
^
drivers/media/video/msm/eeprom/ov5693_eeprom.c: In function ‘ov5693_format_iddata’:
drivers/media/video/msm/eeprom/ov5693_eeprom.c:88:2: error: invalid use of undefined type ‘struct msm_calib_id’
ov5693_id_data.sensor_id= (uint16_t)ov5693_idcalib_data;
^
drivers/media/video/msm/eeprom/ov5693_eeprom.c:88:2: warning: statement with no effect [-Wunused-value]
make[5]: *** [drivers/media/video/msm/eeprom/ov5693_eeprom.o] Error 1
make[4]: *** [drivers/media/video/msm/eeprom] Error 2
make[4]: *** Waiting for unfinished jobs....
LD drivers/media/video/msm/gemini/built-in.o
make[3]: *** [drivers/media/video/msm] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [drivers] Error 2
Am I missing some changes?
Maybe someone know how this can be fixed so everyone gets the same experience.
EDIT:
OK I got it compiling.
https://github.com/drbeat/kernel_lge_v500/commit/7fce6ccd0c82fcdb17c22f4053db4d6703f1c436
Now I need someone with OV5693 to test it out
EDIT 2:
The binaries may be lacking.
I will look into that
EDIT 3:
So I have made a ZIP containing binaries and a kernel with ov5693 drivers
I need someone to test it out
DOWNLOAD: removed!
will upload a new version soon
EDIT 4:
DOWNLOAD: https://www.androidfilehost.com/?fid=95897840722648539
I thought ov5663 was the one that does not work. Here is a log for a ov5693 working with stock AOSP.
http://forum.xda-developers.com/showpost.php?p=57338503&postcount=5
Deltadroid said:
I thought ov5663 was the one that does not work. Here is a log for a ov5693 working with stock AOSP.
http://forum.xda-developers.com/showpost.php?p=57338503&postcount=5
Click to expand...
Click to collapse
there is no "ov5663"
the back camera which is not working is "ov5693"
Then I'm curious why the person who posted that log says his cameras are working.
Deltadroid said:
Then I'm curious why the person who posted that log says his cameras are working.
Click to expand...
Click to collapse
so to clear it up for you
front cam is always "IMX119"
back camera is either "S5K4E5YA" or "OV5693"
there is no "OV5663"
that guy posted dmesg before he flashed AOSP
since his back camera is working he has a "S5K4E5YA" module
just ask him to do another dmesg now. you will see that his results will be IMX119 and S5K4E5YA since AOSP and CM dont support OV5693
Thanks for clearing that up. I'm sure lots of others were/are confused too.
I bet of you changed the title of this thread to something like "fix for back camera" then people would understand the purpose of this thread better and offer to test.
Deltadroid said:
I bet of you changed the title of this thread to something like "fix for back camera" then people would understand the purpose of this thread better and offer to test.
Click to expand...
Click to collapse
i still have to find the right binaries to make a working zip
I have a 50020D, I'll take it for a spin and report back later.
UPDATE: I got stuck at boot logo after flashing, but I managed to restore from my backup.
To tell the truth I'm not using stock CM, but a Team Vanir/Commotio ROM. Although they supposed to be using the same kernel and device tree as CM.
Munszu said:
I have a 50020D, I'll take it for a spin and report back later.
UPDATE: I got stuck at boot logo after flashing, but I managed to restore from my backup.
To tell the truth I'm not using stock CM, but a Team Vanir/Commotio ROM. Although they supposed to be using the same kernel and device tree as CM.
Click to expand...
Click to collapse
thx for reporting
do you have a backcam which is not working?
ckret said:
thx for reporting
do you have a backcam which is not working?
Click to expand...
Click to collapse
Yeah, I do.
It's only working on stock ROMs, so I guess its the same.
If you can tell me how, I can send you a log or something to help you.
uploaded a new zip
this one doesnt give bootloop.
still do a backup and report back please
ckret said:
uploaded a new zip
this one doesnt give bootloop.
still do a backup and report back please
Click to expand...
Click to collapse
I've tried and the tablet booted up well this time, but the fix didn't work unfortunately.
{
"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"
}
can some one that has ov5693 please test this zip and see if the cam works
it uses the same kernel that ckret has in his zip file
the only thing I added was more of the camera binaries from 20d
make sure you back up first
https://www.mediafire.com/?gx83ty2ytxdc2wt
I tried it but it got me into a boot loop.
I hope you figure it out \o
PS: Using Mahdi's Kit Kat Rom.
thanks for testing, sorry about the loop
since I dont have this phone, I dont think I will be able to help much more, sorry
hroark13 said:
can some one that has ov5693 please test this zip and see if the cam works
it uses the same kernel that ckret has in his zip file
the only thing I added was more of the camera binaries from 20d
make sure you back up first
https://www.mediafire.com/?gx83ty2ytxdc2wt
Click to expand...
Click to collapse
its not that simple.
i am writing exams right now so i dont have time look into the problem
ckret said:
its not that simple.
i am writing exams right now so i dont have time look into the problem
Click to expand...
Click to collapse
I looked at your kernel commit and that looked to be right
those files I have in that zip are the correct libraries
what it is probably missing is a key in the lib camera client
there is most likely a message in the logcat that says it could not load camera.msm8960.so because it could not find a key
usually these keys could be added to
frameworks/av/camera/CameraParameters.cpp
and
frameworks/av/include/camera/CameraParameters.h
but then you would have to build cm11 again
I am pretty sure the only way you are going to get the back cam to work is with those libraries
if you grep for ov5693 in the original files / libraries it probably will not be found, if you grep the 20d files, you should find it listed in the mm-qcamera-daemon, liboemcamera.so and the 3 chromatix files
hroark13 said:
I looked at your kernel commit and that looked to be right
those files I have in that zip are the correct libraries
what it is probably missing is a key in the lib camera client
there is most likely a message in the logcat that says it could not load camera.msm8960.so because it could not find a key
usually these keys could be added to
frameworks/av/camera/CameraParameters.cpp
and
frameworks/av/include/camera/CameraParameters.h
but then you would have to build cm11 again
I am pretty sure the only way you are going to get the back cam to work is with those libraries
if you grep for ov5693 in the original files / libraries it probably will not be found, if you grep the 20d files, you should find it listed in the mm-qcamera-daemon, liboemcamera.so and the 3 chromatix files
Click to expand...
Click to collapse
its propably selinux and permission related
this most time cause bootloops
ckret said:
its propably selinux and permission related
this most time cause bootloops
Click to expand...
Click to collapse
idk
would need to see a logcat to be sure