Database Develop

Power Control widget for stock HTC Magic?

I saw from several other threads that there's a "Power Control" widget which toggles wifi/gps/bluetooth/etc on your desktop and is one of the feature in Donut 1.6 ROM, wonder if the widget can be downloaded separately instead of upgrading to a new ROM?

Why would you not want to upgrade to Donut?
The only problem I can think of is compatibility with some apps but I've only experienced one or two problematic apps and they are ones I use rarely. Also it's up to the developers to update their apps now and not users to wait for them.

For now, I'd prefer official ROM for my Magic and since I have the PVT32A version, for the moment, Donut upgrade is out of question for me as it's only PVT32B compatible.
I was thinking that the Power Control Bar could be downloaded as a standalone widget, plus I also read in a thread where someone also said the same too but I just couldn't find any download link for it, so my question is, is there such thing as a "Power Control" widget?

try this
http://www.4shared.com/file/138048564/1936d28c/Settings.html
adb remount
adb install settings.apk
might work

when i adb logcat
i selected widget this is what i get
W/InputManagerService( 156): Window already focused, ignoring focus gain of: co
[email protected]
D/dalvikvm( 489): GC(2) freed 1711 objects / 119648 bytes in 119ms
I/ActivityManager( 156): Displayed activity com.android.settings/.AppWidgetPick
Activity: 3272 ms (total 3272 ms)
D/dalvikvm( 489): GC(2) freed 879 objects / 45832 bytes in 95ms
D/Launcher( 305): dumping extras content=Bundle[{appWidgetId=15}]
W/InputManagerService( 156): Window already focused, ignoring focus gain of: co
[email protected]

[MODS PLEASE DELETE] Notifications disappear

Mods - you can delete this thread as it turns out it is NOT a general issue, but a ROM issue. Thanks!
For some reason, my notifications have started silencing. Ringtones still work - but SMS, Email, etc don't. This effect seems to go away after reboot.
I am a pretty experienced Android user, and have checked volume and sound to make sure they are set right - which they are.
Using Cyanogen 5.0.4.1, but have not had this problem before so I'm thinking it is an app issue.
I don't want to start uninstalling apps willy-nilly...anyone else having this issue?
This is my logcat when a message is received:
Code:
W/Service ( 236): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
W/Service ( 236): setForeground: ignoring old API call on com.wsandroid.Core.BaseService
V/Telephony( 292): getOrCreateThreadId uri: content://mms-sms/threadID?recipient=%2B19793184040
V/Telephony( 292): getOrCreateThreadId cursor cnt: 1
I/power ( 92): *** set_screen_state 0
D/Sensors ( 92): using /dev/input/event6 (name=compass)
D/Sensors ( 92): using /dev/input/event3 (name=proximity)
D/Sensors ( 92): using /dev/input/event0 (name=lightsensor-level)
D/lights ( 92): 0 255 255
D/SurfaceFlinger( 92): About to give-up screen, flinger = 0x14c150
D/AK8973 ( 80): Compass CLOSE

Are you using a dock? If so it's happening to me too. If I reboot and don't use the dock it stops. There was some talk about it in the CM thread as a known issue.

uberingram said:
Are you using a dock? If so it's happening to me too. If I reboot and don't use the dock it stops. There was some talk about it in the CM thread as a known issue.
Click to expand...
Click to collapse
Indeed! Thanks for the pointer.
Mods - you can delete this thread as it turns out it is NOT a general issue, but a ROM issue. Thanks!

[Android 2.1+] SysTune - Optimize under the hood of your system!

{
"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"
}
SysTune
Optimize under the hood of your system!
** Root Rights required!!! **​
This is a system tuning and tweaking tool for advanced users with root access. It allows you to change various system settings to optimize your system.
This is my very first App on the Market. I am open for feedback and try at my best to solve any requests if possible.
It is very advised to properly inform yourself about those settings as i do not take any responsability for any damamge to your device.
NEW FEATURE
Changing priority of processes allows you to prevent lagging or other issues e.g. when a back ground process slow down your phone or you forground app has struggles to do its fluently.
See Help Tab for more informations before using this feature! More Informations and a small Guide will be available in the second or third post in the next days.
Note: The background service for monitoring processes to renice them causes no increased battery drain!
Features:
Changing min/max CPU frequency
Changing cpu governor
Changing advanced governor settings
Voltage Control (SVS and HAVS supported)
Block device settings like IO-Scheduler
Kernel (Scheduler) Tweaks
VM Tweaks
Changing priorities of active processes (renice)
Apply on Boot
Mulit-Core / -CPU support
Realtime CPU Clock Speed and "Time in State"-View of each Core/CPU
Save and load settings individually for each tab (press Menu).
Multi-Core/-CPU supporting CPU Stress Test (New)
Safe Mode ( see in-app Help for Informations )
..... more to come!
NOTE: The availability of the features depends on your system. E.g. if your installed kernel does not provide access to VDD Levels voltage control than it won't be available.
After installation take your time and read the informations on the Help-Tab.
Download on Market
************************************************
If somethings is not working as expected on your device
please post here or email me so that i can fix it for you!
I don't own every device out there
************************************************
​
The zip file for toggling Safe Mode that can be saved on your SD Card via the button in SysTune can also be found here attached to this post.
Thanks to...
Grzesiek Baran for the new Market Feature Image and his Status Bar Icons!
"The Unknown Noob" aka Daniel S. for his Status Bar Icons!

Download User Settings​
This is a section with user contributed settings files for SysTune. Anyone can submit their settings via attachment to a post.
Though i beg to follow some basic rules:
Tell which device, rom (version) and Kernel used
IMPORTANT: Date (and optinal a version number) of your settings. So we now if there was a modification meanwhile!
Short but clear explenation why you use this values
What you did to come to the conclusion to use them
[OPTIONAL] What you changed over the default values of your rom/kernel. (note which were the default values before the change!)
Please follow the rules to make it easier for others to judge if your settings are usefull for them.
A user's settings for CM 10.1 for DHD rom:
Device: Desire HD, Rom: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series - nightly from 20.02.2013
Date: Feb., 20, 2013
No renicing used anymore
Using stock clocks and ondemand governor.
Ondemand Governor settings
Misc settings
A user's settings:
Device: Desire HD, Rom: SCI MIUI 1.11.25v1.0, Kernel: lordmod 8.5 cfs
Date: Nov., 30, 2011
Smoother and more battery friendly then default values.
I am using several benchmark apps to test different aspects. Also i am testing overall daily usage. For reliable tests i have some things i repeat to see how the impact of changes of the settings is. Benchmarks used are: NenaMark 2, An3DBenchXL, Quadrant (not very good though), AnTuTu, TAP Benchmark (for internal flash memory), SD Tools (for sd card).
CPU Settings: ondemand
Governor settings
Misc settings
For BFS kernel version use set rr_interval=2 in the misc tab under kernel settings. But for my Rom i stick to CFS currently.
Renice Settings
Some general tips:
The priorities influence the behaviour when two processes that want to do some work at the same time. It influences which process will get more cpu time, thus it may cause lags for the lower priority process.
So in general the default priority of 0 is the one you should keep for most of the processes. But there are some processes that maybe you are not using all the time, but when you want them to use you want them fast and lag free.An example for this is the "phone" process but also the systemui process can improve the behaviour of your GUI in general.
On the other side there are processes that need to do some work in the background. Such process could slow down or cause lags on your currently used app / foreground process. An example for this is the media scanner "android.process.media". Think of reducing its priority to prevent slowing down other things. You won't care if the media scan in the background would need a minute longer to finish if you get a more fluent foreground app
I also got user reports for apps like media players that since they increased their priority now work flawless.
A User's Renice Settings 12 Dec. 2011 (see used rom etc. above!)
Notess:
I increased the the priority for processes that need to respond fast when they actually are needed, like the phone process.
I also increased the priority of my keyoard app to improve its pop upp in some seldom but annoying situations. If you use more than one keyboard app just set an increased value of all of them. As you never will use two at the same time you do not need to decrease the priority of one of them
Beside of other stuff i also increased the priority of my used launcher, adw ex. Add your launcher or replace my entry with one for your launcher. I think com.android.launcher is the process name for the standard launcher. But as you are using it you can see its process in the list of the "add" dialog.

strange, where has the reply of user sergeybrin gone?
anyway, am open for suggestions and reports of issues. if anybody has tried it found that something is not working for their phone i would be thankfull to know what so i am able to fix that.

Optimal settings for LordMod 7.2BFS kernel
Hi a user thanks for the great app.
I'm on Alienmod's CM7 (nightly 208) with LordMod's 7.2BFS kernel and was wondering what the optimum settings are in the "Governor" tab?
I looked at your MIUI thread and saw that you have:
suspend_freq @ 614400
down_differential @ 15
sampling_down_factor @ 50
ignore_nice_load @ 0
up_threshold @ 85
powersave_bias @ 50
sampling_rate @ 80,000
io_is_busy @ 1
so I am using these settings and everything seems ok.. (im using ondemandX 230400min and 1152000max).
Are these settings ok to use for my ROM or are there better settings?
Also i'm currently -50mV undervolted.
Thanks!!

this are still the settings i use and i think they pretty much optimal for aosp roms for the dhd. edit: except that my max fre is 1075MHz
regarding undervolting: carefull and you should only undervolt one freq at a time then test that extesively (e.g. by setting min and max freq to it and running something stressing the cpu for a longer time).
in general it is only needed to undervolt the freqs close to your set max freq as undervolting only makes a significant difference on consumption if there is high load. and on high load your phone switches to higher freqs
p.s. glad you are happy with the app.

I recently discovered due to a nice customer that despite googles license code documentation the licensing server do not provide validation timeout infos. hence some customers may observed that the app failed licensing on connection issues.
Google documentation on this claimed it should work as i expected but it doesn't. Hence i just fixed this now myself and want to apologise for any issues caused by this. I will improve this further in the near future.

Great App

thank you!
@all: There are many roms out there with broken busybox installations. i already have some workaround built in to handle that. i just discovered that one of my workaround had a typo. so if someone tried the app and saw it not working as it should it probably got fixed with the most recent update to 1.2.6.
i would like to see why some people are cancelling the purchase as it is already possible to see exactly what it does on the screen shots. If something is not working as it should i can't fix it without feedback. too many roms and devices out there to have them all and being able to test against.

I've tested unsuccessfully on the tmo g2x running EaglesBlood latest (cm7 based) and the dragon kernal. By testing I mean the drop downs for CPU Max and min show a thin white bar with nothing selectable.
Edit: tested with another kernal, and my guess is they don't support your method for accessing the processors... but I've been wrong before.

thank you for the feedback. But i need the info provided by the feedback button. Please use the feedback button on the help tab to collect some information and send it via email.
if you do not want to send me an email you canstill use that button. it will collect some infos and save them on your sdcard as "systune.inf". cancel the email that opens up. the file will still remain on your sdcard.
attach it here to your next post (maybe you need to rename its extension to .txt). without that info there is nothing i could do.
p.s. you can look into that file to verify that nothing confidential is collected. it is plain text.
EDIT: i saw your edit. does this mean with the other kernel it worked? basically your guessing seems right. but the thing is that my method to acces this values is the ONLY one possible. it is done through the kernel exported values in the sysfs. this is basically the only way to access kernel values at runtime. this custom kernel(s) you are using are either not exporting these stuff or they are doing wrong (by convention).
in the latter case at least i could do a workaround to compensate for their wrong placement of the stuff.

The Load Settings dialog box is not working on BlackIce, same problem as I had on Hydr0g3nmod before. Box just displays Cancel and nowhere to select a file to load. Not critical but would be nice to have. Probably due to the super dark theme. Thanks!
Sent from my Desire HD using Tapatalk

cold y verify that it is indeed only due to the theme? i mean try pressing in the middle of the box where normally the entry of a file to load is located and see if it loads.
if it is just a theme issue, dark text on dark background, then you should inform paradoxx or alienmind about this as this is a bug on their rom. i am simpy using system default theme.
usefull for them to know is that the items to load are listed in a ListView using "android.R.layout.simple_list_item_1" for the items. With these infos they should be able to fix their theme.
p.s. new version with new features coming very soon.

a user said:
cold y verify that it is indeed only due to the theme? i mean try pressing in the middle of the box where normally the entry of a file to load is located and see if it loads.
if it is just a theme issue, dark text on dark background, then you should inform paradoxx or alienmind about this as this is a bug on their rom. i am simpy using system default theme.
usefull for them to know is that the items to load are listed in a ListView using "android.R.layout.simple_list_item_1" for the items. With these infos they should be able to fix their theme.
p.s. new version with new features coming very soon.
Click to expand...
Click to collapse
Thanks, no luck in finding the hidden dialog box but no big deal.I'll wait until the BlackIce theme fix is done, or who knows perhaps I'll be back on sci miui by then
Sent from my Desire HD using Tapatalk

New version with new features available.
Now it supports various kernel tweaks (cfs scheduler tweaks) and vm tweaks. You can find them in the Misc Tab. Also saving/loading is now available for the Misc Tab.

Hi my8,
Do you think that it could be useful to discuss our findings about the tuning of some parameters here or in another section?
Thanks for your VERY useful app.

normally i would say this should be in a device specific thread. but because i wont be allowed to open up a systune thread in each device subforum i think we could do it here.
so feel free to be the first.
as basic rules i think one should always include infos about device/rom/kernel to make the post actually usefull.

new version 1.3.2:
added tunable paramter for BFS kernels in the Kernel settings section under the Misc tab.

a user said:
normally i would say this should be in a device specific thread. but because i wont be allowed to open up a systune thread in each device subforum i think we could do it here.
so feel free to be the first.
as basic rules i think one should always include infos about device/rom/kernel to make the post actually usefull.
Click to expand...
Click to collapse
Ok thanks for that and also for v1.3.2.
I think also that here could be a good place for the discussion of some of the tunable parameters via systune app. Indeed, I think that there should be no such big difference from ROM to ROM (but probably more from device to device...).
This offers also the possibility to give (and get) some information about the parameters that are tunable via Systune.
Among the different group of parameters, due to personal interest, I want to focus on scheduler ones (CFS and now BFS (since v1.3.2)).
And first of all, some theory, because before tuning anything, it is EXTREEMELY IMPORTANT TO UNDERSTAND the meaning of these parameters: here below is a partial copy of http://doc.opensuse.org/products/opensuse/openSUSE/opensuse-tuning/cha.tuning.taskscheduler.html about CFS in opensuse distribution.
NB: I am not an expert in Android, but IMHO I thing that even if Android runs on linux, it must be a lot of difference between running a phone and a desktop. It is why, it is interesting to have this kind of discussion here.
The comment are personal and are there just to start the discussion....
My phone is a HTC Desire HD, with blackIce ROM with LordMod UE kernel v8 CFS.
sched_child_runs_first
A freshly forked child runs before the parent continues execution. Setting this parameter to 1 is beneficial for an application in which the child performs an execution after fork. For example make -j<NO_CPUS> performs better when sched_child_runs_first is turned off. The default value is 0.
OK default value seems logical for me.
sched_compat_yield
Enables the aggressive yield behavior of the old 0(1) scheduler. Java applications that use synchronization extensively perform better with this value set to 1. Only use it when you see a drop in performance. The default value is 0.
OK default value seems logical for me, but Dalvik being a Java VM, 1 could also be logical ?????
Expect applications that depend on the sched_yield() syscall behavior to perform better with the value set to 1.
sched_migration_cost
Amount of time after the last execution that a task is considered to be “cache hot” in migration decisions. A “hot” task is less likely to be migrated, so increasing this variable reduces task migrations. The default value is 500000 (ns).
If the CPU idle time is higher than expected when there are runnable processes, try reducing this value. If tasks bounce between CPUs or nodes too often, try increasing it.
In case of single core processor, IMHO I think that this value must be set high....
sched_latency_ns
Targeted preemption latency for CPU bound tasks. Increasing this variable increases a CPU bound task's timeslice. A task's timeslice is its weighted fair share of the scheduling period:
timeslice = scheduling period * (task's weight/total weight of tasks in the run queue)
The task's weight depends on the task's nice level and the scheduling policy. Minimum task weight for a SCHED_OTHER task is 15, corresponding to nice 19. The maximum task weight is 88761, corresponding to nice -20.
Timeslices become smaller as the load increases. When the number of runnable tasks exceeds sched_latency_ns/sched_min_granularity_ns, the slice becomes number_of_running_tasks * sched_min_granularity_ns. Prior to that, the slice is equal to sched_latency_ns.
This value also specifies the maximum amount of time during which a sleeping task is considered to be running for entitlement calculations. Increasing this variable increases the amount of time a waking task may consume before being preempted, thus increasing scheduler latency for CPU bound tasks. The default value is 20000000 (ns).
For a phone running with a processor > 1GHz I thing that 5000000 is a good value (to be discussed further)
sched_min_granularity_ns
Minimal preemption granularity for CPU bound tasks. See sched_latency_ns for details. The default value is 4000000 (ns).
Same as above with a suggested value of 1000000
sched_wakeup_granularity_ns
The wake-up preemption granularity. Increasing this variable reduces wake-up preemption, reducing disturbance of compute bound tasks. Lowering it improves wake-up latency and throughput for latency critical tasks, particularly when a short duty cycle load component must compete with CPU bound components. The default value is 5000000 (ns).
Same as above with a suggested value of 1000000
sched_nr_migrate
Controls how many tasks can be moved across processors through migration software interrupts (softirq). If a large number of tasks is created by SCHED_OTHER policy, they will all be run on the same processor. The default value is 32. Increasing this value gives a performance boost to large SCHED_OTHER threads at the expense of increased latencies for real-time tasks.
IMHO must be sed = 0 for single core processor....
[To be continued later.....]

I know this article already but good you posted it here.
Based on my understanding an tests i have the following suggestions:
Sched_compat_yield set to 0 seems to improve performance. Note this is not a java virtual machine. This is only based on my tests
Sched_latency_ns : I recently am testing very low values. Currently using 390000 and 130000 for the two granularity parameters.
It seems smoother without losing raw throughoutput performance.
Regarding the migration parameters.... we are running a single core device. hence I think it simply doesn't matter what values we have set there as no task will ever switch the CPU it is bound to.
But a test if set to 0 can reduce some overhead could be a worth try.
Sent from my HTC Desire HD using XDA App

a user said:
I know this article already but good you posted it here.
Based on my understanding an tests i have the following suggestions:
Sched_compat_yield set to 0 seems to improve performance. Note this is not a java virtual machine. This is only based on my tests
Sched_latency_ns : I recently am testing very low values. Currently using 390000 and 130000 for the two granularity parameters.
It seems smoother without losing raw throughoutput performance.
Regarding the migration parameters.... we are running a single core device. hence I think it simply doesn't matter what values we have set there as no task will ever switch the CPU it is bound to.
But a test if set to 0 can reduce some overhead could be a worth try.
Sent from my HTC Desire HD using XDA App
Click to expand...
Click to collapse
Ok and thanks for your answer even if I don't totally agree with your proposal.
Indeed, I think that going down to so small value could be a little bit risky in term of CPU load and throughput for processor bounded task (I know that they are quite unimportant in a phone). Nevertheless, I am now testing Sched_latency_ns 1000000 and 250000 for the two granularity parameters...
Now some words about BFS ( Brain **** Scheduler) introduced recently by M. Kolivas (see article here: http://ck.kolivas.org/patches/bfs/sched-BFS.txt).
"It was designed to be forward looking only, make the most of lower spec machines, and not scale to massive hardware. ie it is a desktop orientated scheduler, with extremely low latencies for excellent interactivity by design rather than "calculated", with rigid fairness, nice priority distribution and extreme scalability within normal load levels."
Here the only tunable parameter is rr_interval that is roughly equivalent to the latency [in ms]. The default value = 6 [ms] that seems ok for me (possible values 1 -> 1000).
[to be continued...]

[MOD] Getting tablet UI on CM9

Since I saw some people wants tablet UI on mirroring or lapdock,
I made a file for Atrix's CM9 based on this thread.
http://forum.xda-developers.com/showthread.php?t=1467051
I didn't post a screenshot cause you can see it at link.
Every UI will change to that of tablet, and every app will act as tablet.
So here's the steps you have to do.
http://api2.ge.tt/0/81rFJED/0/blob/download
1. Download services.jar and overwrite it to /system/framework.
(Of course, need 644 permission.
If you are not sure, see other file's permission in folder.)
(This file is based on alpha 7)
2. Open /system/build.prop
3. Find the line 'ro.build.characteristics=default'
and change the 'default' to 'tablet'
4. Set the screen density to 120 by changing
'ro.sf.lcd_density=240' to 'ro.sf.lcd_density=120'
5. Save and reboot.
6. You will get tablet UI
So, If you want to get back,
just change your density to 240 and it will revert to phone UI.
We need reboot between UI change now,
but maybe devs can do some mod after CM9 have all feature

Awesome but, it doesn't look very good on the lap dock - there is something wrong with the resolution. Im sure it will be fixed.
Additionally if the phone could switch the UI from Phone to Tablet when HDMI is connected it would be an awesome way to ditch the awful Webtop.

+1 Thanks to you man!!
was trying to do this by editing the services.jar, this is WONDERFUL.
if possible can you tell me how to do a PM? (where changing the file classes), baksmali, simali need not only change which line ...

soluttion calls
folks, you should now be aware that the "app called" force close, I've tried the app (phone) several roms without success .. == force close when calling ==
ps: but the calls continue in the background!
some options:
1 - ShakeCall (has other apps)
2 - accessibility options = end call button poweer

This is cool!
I tried it, its like having a small tablet....
Just a pitty about the phone UI, its not actually usuable like that!
Whatching for development

I see great potential in this.
If we could autoscript something, where if the phone recognises that it's been connected via HDMI (for mirroring), then it automatically changes into tablet UI. That'll be so freakin awesome! And it'll be a good webtop replacement for CM9!

Notorious544d said:
I see great potential in this.
If we could autoscript something, where if the phone recognises that it's been connected via HDMI (for mirroring), then it automatically changes into tablet UI. That'll be so freakin awesome! And it'll be a good webtop replacement for CM9!
Click to expand...
Click to collapse
Thats what I've been saying...

Notorious544d said:
I see great potential in this.
If we could autoscript something, where if the phone recognises that it's been connected via HDMI (for mirroring), then it automatically changes into tablet UI. That'll be so freakin awesome! And it'll be a good webtop replacement for CM9!
Click to expand...
Click to collapse
+1
I thought somebody was already working on this.
Sent from my MB860 using xda premium

try
is usable but ...
set large fonts ...
do not set the lcd_density so small, it can be adjusted, try 140 .... (I think)
I find it very usable ... hopefully someone with enough knowledge to resolve calls ...
D/AudioMgrRIL( 1321): setting volume, volume = 6
I/AudioService( 1469): AudioFocus requestAudioFocus() from AudioFocus_For_Phone_Ring_And_Calls
D/lights ( 1469): RGB: "attention", color=0x00000000, flash=2, onMs/offMs=0/0 => blink=0, RGB=0 0 0
D/CallNotifier( 2693): showIncomingCall()... phone state = OFFHOOK
D/dalvikvm( 2693): GC_CONCURRENT freed 358K, 27% free 6530K/8839K, paused 2ms+2ms
D/lights ( 1469): LCD: SENSOR, 88 * 1.00 => 88
D/lights ( 1469): LCD: SENSOR, 82 * 1.00 => 82
D/lights ( 1469): LCD: SENSOR, 75 * 1.00 => 75
D/lights ( 1469): LCD: SENSOR, 69 * 1.00 => 69
D/dalvikvm( 2693): GC_CONCURRENT freed 422K, 27% free 6653K/9031K, paused 1ms+2ms
D/lights ( 1469): LCD: SENSOR, 63 * 1.00 => 63
D/lights ( 1469): LCD: SENSOR, 56 * 1.00 => 56
I/ ( 1400): odm_disp_esd_thread is running(200) state=1
D/lights ( 1469): RGB: "attention", color=0x00ffffff, flash=2, onMs/offMs=7/1000 => blink=1, RGB=255 255
255
D/lights ( 1469): LCD: SENSOR, 50 * 1.00 => 50
D/lights ( 1469): RGB: "attention", color=0x00000000, flash=2, onMs/offMs=0/0 => blink=0, RGB=0 0 0
D/lights ( 1469): LCD: SENSOR, 44 * 1.00 => 44
D/lights ( 1469): LCD: SENSOR, 37 * 1.00 => 37
D/lights ( 1469): RGB: "attention", color=0x00000000, flash=0, onMs/offMs=0/0 => blink=0, RGB=0 0 0
I/CustomSpnReader( 2693): operatorNumberic = 72402
I/CustomSpnReader( 2693): oriSpnName = TIM
I/CustomSpnReader( 2693): Current language is : pt
E/CustomSpnReader( 2693): Config File Path : /system/etc/spn-conf.xml
D/lights ( 1469): LCD: SENSOR, 31 * 1.00 => 31
D/lights ( 1469): LCD: SENSOR, 25 * 1.00 => 25
I/CustomSpnReader( 2693): expression : /spnOverrides/spnOverride[@numeric='72402']
W/ActivityThread( 2693): ClassLoader.getResources: The class loader returned by Thread.getContextClassLoa
der() may fail for processes that host multiple applications. You should explicitly specify a context cla
ss loader. For example: Thread.setContextClassLoader(getClass().getClassLoader());
D/lights ( 1469): LCD: SENSOR, 18 * 1.00 => 18
E/CustomSpnReader( 2693): Not Found : 72402 in spn-conf.xml
D/lights ( 1469): LCD: SENSOR, 12 * 1.00 => 12
D/ComprehensiveCountryDetector( 1469): onServiceStateChanged
D/lights ( 1469): LCD: SENSOR, 6 * 1.00 => 6
D/lights ( 1469): LCD: SENSOR, 0 * 1.00 => 0
I/power ( 1469): *** set_screen_state 0
D/lights ( 1469): buttons: USER, 0
D/SurfaceFlinger( 1318): About to give-up screen, flinger = 0xf918
D/ ( 1400): NVRM_DAEMON(1137): pm_notifier_thread: calling power_displays(false)
I/ ( 1400): DispMgr recv'd NvDispMgrDisplayAttr_Suspend
I/ ( 1400): called NvDispMgrAttrSetTranslate() from attr_common err=0
I/ ( 1400): DispMgr recv'd NvDispMgrDisplayAttr_Suspend
I/ ( 1400): called NvDispMgrAttrSetTranslate() from attr_common err=0
D/ ( 1400): NvDdkDispBacklightTimeout() thread running
I/ ( 1400): enter motDsiSetMode
I/ ( 1400): exit motDsiSetMode
I/ ( 1400):
I/ ( 1400): enter motDsiSetPowerLevel
I/ ( 1400): enter motDsiSuspend
I/nvrm_daemon( 1394): NVRM_DAEMON(1137): pm_notifier_thread: calling power_displays(false)
E/AudioHardwareMot( 1321): Error:Unsupported key = tty_mode=tty_off
D/dalvikvm( 2693): GC_CONCURRENT freed 425K, 27% free 6718K/9095K, paused 3ms+2ms
I/ ( 1400): exit motDsiSuspend
I/ ( 1400):
I/ ( 1400): exit motDsiSetPowerLevel
I/ ( 1400):
D/ ( 1400): NVRM_DAEMON(1140): pm_notifier_thread: returned from power_displays(false)
I/nvrm_daemon( 1394): NVRM_DAEMON(1140): pm_notifier_thread: returned from power_displays(false)
E/AudioHardwareMot( 1321): Error:Unsupported key = screen_state=off
E/DefaultVoicemailNotifier( 2419): No voicemails to notify about: clear the notification.
D/AccelerometerListener( 2693): orientation: horizontal
D/MccTable( 2693): updateMccMncConfiguration: mcc=724, mnc=2
D/MccTable( 2693): locale set to null_br
D/MccTable( 2693): WIFI_COUNTRY_CODE set to br
I/WifiService( 1469): WifiService trying to set country code to br with persist set to true
D/dalvikvm( 1469): GC_EXPLICIT freed 558K, 31% free 9601K/13767K, paused 4ms+5ms
D/dalvikvm( 2693): GC_CONCURRENT freed 421K, 26% free 6839K/9223K, paused 2ms+3ms
D/Tethering( 1469): MasterInitialState.processMessage what=3
D/PicasaSyncManager( 2253): active network: null
D/PicasaSyncManager( 2253): background data: true
I/MediaUploader( 2232): No need to wake up
Click to expand...
Click to collapse
seems an error of speakers, and also a file in system/etc/spn-conf.xml

WOW
I would love to have this ability. I am not a huge fan of the webtop as is, and if there was a method to use this UI through the HDMI connection (especially through a lapdock) I could see some cool things happening.

Only thing that stopped me from using this is that I can't use the phone
Sent from my MB860 using XDA App

The phone capability would be awesome to have, and I wouldn't doubt that the extremely talented DEV people could find a way to make that work, but no phone isn't a deal breaker for me.
I tried to get awareness of this in the CM9 thread of jokersax, but there is more important talk going on over there at the moment. Hopefully someone will pick up this project further, and make it available to those who want it (and hopefully add in the missing functionalities).
The UI experience I think would clean up the overall install of things on the phone, get rid of the webtop and/or separate OS installation, and provide one OS that will be used for both the phone and a docking experience.
We'll see though .

I can start working on this, this weekend, I've been busy working on a small version of vector Linux that runs through vnc on the lap dock.
Sent from my MB860 using XDA App

Use buildroot or OpenEmbedded to keep it light as possible, plus you can optimize the compiler flags for tegra
Sent from my MB860 using XDA App

OK, hadn't thought of build root, the only thing I'm having a little trouble is getting it to mount the 32 gb SD card, even after partitioning it for vector. Sometimes it'll mount. Some times mope
Sent from my MB860 using XDA App

Mount loop img, I preffer it over reformating the SD card
Also check out Linux for Tegra from nVidia
Sent from my MB860 using XDA App

Will do, thanks
Sent from my MB860 using XDA App

I don't sure if it's possible, but can we run vnc server on android and connect from Chroot/vnc environment. Sort of vnc in vnc. If it's possible we can use it instead aiw application.
Sent from my MB860 using XDA App

I can try that when I get home, but I don't think it'll work.
Sent from my MB860 using XDA App

Heck Yeah
I started up the talk again! haha
Thanks guys for talking/looking into getting this to work. Hopefully bumping this post will get people to check into this more, and be guinea pigs for the testing.
Unfortunately, my schedule and how I use my phone doesn't allow me the time to easily help out with testing things, and I apologize about that ahead of time.
Keep up the good work, and please keep us informed!
Also, I'm not sure if the thread creator would get upset with you working on his stuff (and publishing it for testing, or whatever) without proper consent. Just wanted to throw that out there, just in case. I don't want to see the progress on things to be thwarted due to something as trivial as getting a "verbal" OK to work on making something better.
Thanks for the time all!

[APP][NST/G] Quick Tiles

*6-17-23 Updated to 2.2*
--removed dependency on ScreenShotEasy
--added small binary file to convert frame buffer contents to png image
If you are updating, you must uninstall the previous version and read below as the app function has changed starting with 2.0.
The Quick Tiles app is an implementation for the NST/G of a now ubiquitous feature of modern Android systems. In this version for the NST/G, the user may select and arrange up to eight "tiles" which are shortcuts to features such as WiFi, screen orientation, NoRefresh, FastMode, and others. You may also edit the selection and arrangement of the tiles via the panel itself (the "pencil"--see screenshot below). I've tried to keep the selection of options focused on the typical areas of display and connectivity, although I have included some mode functions as well, such as display refresh modes and USB host. I welcome suggestions for additional options, but would discourage trying to make a "launcher" application out of what should be shortcuts to basic functions.
General Requirements
1. Root. A number of tiles require root to access shell commands or something else generally off limits to typical user access. Root permission is required only once, however, since it's all one app. The quickest way to get this over with is a long-press on the WiFi tile. This tries to access the WiFi Settings section of the Settings app and so needs root access. Once you've approved that, anything else will be OK.
2. This is a Tasker-generated app. If you already have one of my other Tasker-generated apps, you don't need the two Google maps library files included in the zip and can delete them. If you do need them, copy the two files into the locations shown below:
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the app will not install.
3. Copy the binary file "fb2png" to /data/local, permissions rwx rx rx
4. Copy the folder "QTiles" (and its contents) from the zip to the root of your SD card.
5. Because it is used (by Tasker) as a plugin, RotationLocker is a dependency of the app. It must be installed whether you use that feature or not.
6. Copy the QuickTiles apk file to your SD card and install via a file manager or install via ADB.
Setup
This app includes all the functionality of many other small apps I have put together. As such, it needs many of the configuration measures and/or plugins for those apps (but not the actual apps themselves such as USB Audio, Screenshot, ES Remote Manager, RN Menu, WiFi Menu, etc.--any of these other apps may be uninstalled if you are using Quick Tiles). As supplied, the app is configured to show only the WiFi tile (option wifi1). This configuration information is stored in the file QTiles/qtiles.txt:
Code:
wifi1,blank,blank,blank
You can edit this file on the NST/G with a text editor or on your PC.
New in version 2.x
To enable Quick Tiles, tap on the icon after installation. You will eventually see a message that the app is enabled. This means there is now a transparent overlay which covers the status bar from the right edge of the "menu" button to approximately the clock. The stock "hot spot" for the WiFi/Glowlight dialog extends fully over the clock. I stopped my overlay before the clock to allow access to bookmarking in the stock reader. So if you've gotten used to tapping in the upper right corner for WiFi/Glowlight, you'll need to relearn the motion. What you gain (besides Quick Tiles) is the possibility of assigning some other function to "clock" using NTMM, although it won't work in the Reader. Meanwhile, Quick Tiles will work in the Reader as well as everywhere else, whether the status bar is visible or not. Also, enabling Quick Tiles means that if you reboot, the transparent overly will reappear (shortly) without any additional action on your part (i.e., you never need to tap on the app icon again). To open the panel, just tap on the status bar between the "menu" button and the clock. You can close the panel manually by swiping upward (a little clumsy) or tapping on the small arrow at bottom center.
There are potential hazards associated with blocking areas of the screen, even apparently "blank" areas of the status bar. During testing I found at least one app that used the "hot spot" area when in full-screen mode: QuickPic. Editing and other tools appear in that area and are blocked by the transparent overlay of QuickTiles. My solution was to add an "escape" of sorts. If you long-press on the "hot spot" you will shortly see a toast stating that the app is disabled for 1 minute. This allows access to potentially blocked spots some apps may use.
----------------------------------------------------------------------------------------------------------------------------
When the Quick Tiles panel is open, a long-press on the pencil icon in the lower right will attempt to open the configuration file for editing. If you choose whatever text editor you have as the default for a .txt file, the next time you access this function the file will open immediately (ES Note Editor, a part of ES File Explorer, is a great simple text editor). Changes in the configuration are immediate, i.e., the next time you open the panel, you will see the new arrangement. YOU MUST SELECT A MULTIPLE OF FOUR TILES, INCLUDING BLANKS (i.e., either 4 or 8 tiles).
All the tile options are listed below, along with links for configuration information and download links for apps used as plugins. These are also the names to be used in the configuration qtile.txt file as well as the names of icon files in Qtiles/icons (if you hate my icons, you may design your own, as long as you adhere to the same size of transparent png). By their nature, some tiles require the panel to close before execution. Actions which display alerts or dialogs are examples. Others (such as WiFi) can operate either with auto-close of the panel or without. It's your choice. I find myself often wanting something else after starting WiFi, so I have that tile set for manual close. Where this is an option there are two identical icons such as wifi1 and wifi2. The option with the "1" will auto-close the panel in every case. If you choose the option with the "2", you can close the panel yourself with an upward swipe or the little arrow.
Note: where an app is required, you only need to install it if you are going to use that function. This does not include RotationLocker which is a dependency.
blank
Place-holder. It should be used to make a full count of four (one row) or eight (two rows), if you are using fewer than a full row. It could also be used for spacing.
clearscreen
Uses the Nook Clear Screen app as a plugin (download).
fastmode1/2
Toggle shortcut to FastMode2 (the original FastMode has a different package name and will not work). It behaves exactly the same way as tapping on the regular FastMode icon. You must have FastMode2.apk installed (download) as well as a kernel that supports this display mode.
ftp
Shortcut to the Remote Manager function of ES File Explorer. WiFi must be on for this to work. Termination of the Remote Manager is handled through the notification window. You must have some version of ES File Explorer installed (download).
glowlight
Duplicates the behavior of QuickNav button #5 (default) for the NSTG, calling up the GlowLight control panel.
glowtoggle
Toggles the light off/on with a tap. A long-press calls up the GlowLight control panel.
Note: this option assumes you have not reassigned a long-press of the "n" button to anything but the Glowlight. Otherwise, a tap on the icon will call up whatever alternative you have selected.
input
Calls up the Android 2.1 keyboard selector. Keyboard apps should be placed in /system/app and permissions set to rw-r-r.
norefresh1/2
Toggle shortcut to NoRefresh (the package names for the two versions of the app are apparently the same so whichever you have should work). It behaves exactly the same way as tapping on the regular NoRefresh icon. Generally you don't need this, but those of us who use NoRefresh know that it sometimes just drops out! You must have either of the two NoRefresh apps installed (download) as well as a kernel that supports this display mode. Note: this assumes you have all the automatic/gesture options disabled. The contrast adjustment is OK, but the rest causes all kinds of trouble.
reboot
Calls up a dialog similar to the stock shut down dialog. If reboot is confirmed, executes a complete reboot from the "Read Forever" screen.
rotation
Toggle (default portrait) that uses the Rotation Locker app to change the screen orientation. Landscape mode is locked in by using a notification/background service. It is best not to exit landscape via the notification since that will probably confuse the toggle variable. Return to portrait should be done via the Quick Tile. Requires RotationLocker app (download).
screenshot
Uses /data/local/fb2png to take a screenshot and then displays a brief, smaller version of the screenshot as well as a notification. Images are saved to /sdcard/Pictures/Screenshots. Create folders if they don't exist already.
usbaudio
Toggle which starts/stops USB audio service and prompts for the appropriate connections before displaying on-sceen media volume controls. Requires a kernel supporting USB host, additional patches for audio, as well as phone.apk in system/app for media volume control.
usbhost
Toggle which starts/stops USB host service and prompts for the appropriate connections. Requires a kernel supporting USB host.
wifi1/2
Toggle which bypasses the B&N WiFi Quick Settings dialog. If WiFi is off, it turns it on. If it's on, it turns it off. A long-press on this tile turns on the WiFi radio and opens the WiFi Settings menu for occasions when you need to select and log on to an unfamiliar network.
Note that something like wifi1/2 in the list above actually represents two different options, wifi1 and wifi2

Heads up, the RotationLocker link on this is dead, 403 forbidden

alexhorner said:
Heads up, the RotationLocker link on this is dead, 403 forbidden
Click to expand...
Click to collapse
Try again. I just downloaded from the link.

nmyshkin said:
Try again. I just downloaded from the link.
Click to expand...
Click to collapse
No luck here. It downloads an apk file which contains the contents of the 404 page.
Tried in another browser logged out, logged in, etc

alexhorner said:
No luck here. It downloads an apk file which contains the contents of the 404 page.
Tried in another browser logged out, logged in, etc
Click to expand...
Click to collapse
Ah. I didn't look at the file. Try this https://forum.xda-developers.com/attachments/rotationlocker_mod-apk.5088219/

nmyshkin said:
Ah. I didn't look at the file. Try this https://forum.xda-developers.com/attachments/rotationlocker_mod-apk.5088219/
Click to expand...
Click to collapse
That one worked, thanks!
Got QuickTiles installed now. Very happy with it, makes some functions much easier to handle.
Is it possible to move the files from the SD to the system? I don't keep an SD card with my nook right now as I am constantly rewriting it for testing.

alexhorner said:
That one worked, thanks!
Got QuickTiles installed now. Very happy with it, makes some functions much easier to handle.
Is it possible to move the files from the SD to the system? I don't keep an SD card with my nook right now as I am constantly rewriting it for testing.
Click to expand...
Click to collapse
Mmm....it's probably possible. Fortunately I still have all the bits on my KitKat device (Tasker AppFactory will not run on Eclair, not even version 1) from just updating the app. As it happens this is something I'm looking into for my weather widget which I've been doing some update work on when not putting out fires in the Forest of Arden (BTW, the other UK "helpee" managed nicely on a second try with your directions, so thanks from both of us). I believe moving its folder to /media will resolve an issue present since version 1, but I've gotten bogged down in other issues and haven't tried it yet. I'm also working on a mod of Mantano Reader, so the little grey cells get a bit jumbled at times.
Let me see if I can quickly change all the references from "sdcard" to "media" and recompile. It may take a day and I probably won't test it. I'll leave that to you. Meanwhile, you clearly need a couple of sdcards.

nmyshkin said:
Mmm....it's probably possible. Fortunately I still have all the bits on my KitKat device (Tasker AppFactory will not run on Eclair, not even version 1) from just updating the app. As it happens this is something I'm looking into for my weather widget which I've been doing some update work on when not putting out fires in the Forest of Arden (BTW, the other UK "helpee" managed nicely on a second try with your directions, so thanks from both of us). I believe moving its folder to /media will resolve an issue present since version 1, but I've gotten bogged down in other issues and haven't tried it yet. I'm also working on a mod of Mantano Reader, so the little grey cells get a bit jumbled at times.
Let me see if I can quickly change all the references from "sdcard" to "media" and recompile. It may take a day and I probably won't test it. I'll leave that to you. Meanwhile, you clearly need a couple of sdcards.
Click to expand...
Click to collapse
Managed to find another SD card but I would still like it to run without certainly. No rush on it!

alexhorner said:
Managed to find another SD card but I would still like it to run without certainly. No rush on it!
Click to expand...
Click to collapse
Give the attached apk a try. Best to uninstall the old one first, move the Qtiles folder and contents to /media and then install the new app. Tap on the icon and see what happens. As I said, I did not test this, but I think I caught all the directory changes. Unless there is an access issue, it should function.

nmyshkin said:
Give the attached apk a try. Best to uninstall the old one first, move the Qtiles folder and contents to /media and then install the new app. Tap on the icon and see what happens. As I said, I did not test this, but I think I caught all the directory changes. Unless there is an access issue, it should function.
Click to expand...
Click to collapse
No luck after a few attempts inclusing a reboot I'm afraid. Attached is the logcat which complains of some failed link creations:
Spoiler: QuickTiles 2.0 Internal Logcat
I/PowerManagerService( 1053): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 1053): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 1053): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/PowerManagerService( 1053): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
I/ActivityManager( 1053): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x14000000 cmp=com.home.nmyshkin.quicktiles/net.dinglisch.android.tasker.Kid }
I/ActivityManager( 1053): Start proc com.home.nmyshkin.quicktiles for activity com.home.nmyshkin.quicktiles/net.dinglisch.android.tasker.Kid: pid=1645 uid=10029 gids={}
E/TC ( 1295): KPICollector: 1634499255283 platform process_start {"processName":"com.home.nmyshkin.quicktiles"}
I/dalvikvm( 1645): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
I/dalvikvm( 1645): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=60)
E/TC ( 1295): KPICollector: 1634499255317 ActivityManager background {"component":"com.gacode.relaunchx/.AllApplications"}
E/TC ( 1295): KPICollector: 1634499255319 ActivityManager foreground {"component":"com.home.nmyshkin.quicktiles/net.dinglisch.android.tasker.Kid"}
D/ ( 1645): unable to unlink '/data/data/com.home.nmyshkin.quicktiles/shared_prefs/net.dinglisch.android.tasker.preffy.xml.bak': No such file or directory (errno=2)
D/dalvikvm( 1645): GC freed 7905 objects / 350624 bytes in 39ms
D/dalvikvm( 1645): GC freed 9893 objects / 366576 bytes in 39ms
D/dalvikvm( 1645): GC freed 10583 objects / 379016 bytes in 40ms
D/dalvikvm( 1645): GC freed 8001 objects / 204056 bytes in 55ms
I/global ( 1645): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 1645): GC freed 11001 objects / 538824 bytes in 45ms
D/LocationManager( 1645): Constructor: service = [email protected]
D/dalvikvm( 1645): GC freed 1040 objects / 176368 bytes in 50ms
I/global ( 1645): Default buffer size used in BufferedReader constructor. It would be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 1645): GC freed 1018 objects / 252120 bytes in 40ms
D/ ( 1645): unable to unlink '/data/data/com.home.nmyshkin.quicktiles/shared_prefs/net.dinglisch.android.tasker.statey.xml.bak': No such file or directory (errno=2)
D/dalvikvm( 1645): GC freed 3917 objects / 222192 bytes in 43ms
D/dalvikvm( 1645): GC freed 6271 objects / 196128 bytes in 51ms
D/dalvikvm( 1645): GC freed 13055 objects / 517832 bytes in 56ms
D/dalvikvm( 1645): GC freed 44936 objects / 1603840 bytes in 64ms
W/InputManagerService( 1053): Window already focused, ignoring focus gain of: [email protected]
D/dalvikvm( 1645): GC freed 5770 objects / 288336 bytes in 49ms
D/ ( 1645): unable to unlink '/data/data/com.home.nmyshkin.quicktiles/shared_prefs/net.dinglisch.android.tasker.varry.xml.bak': No such file or directory (errno=2)
D/dalvikvm( 1645): GC freed 1148 objects / 83472 bytes in 40ms
D/ ( 1645): unable to unlink '/data/data/com.home.nmyshkin.quicktiles/shared_prefs/net.dinglisch.android.tasker.fixy.xml.bak': No such file or directory (errno=2)
V/Activity( 1362): performResume()
D/EPD#ActivityResume( 1053): resetRegion 4
D/NATIVE-EPD( 1053): epd_reset_region: 0x10
D/EPD#ActivityResume( 1053): resetRegion 5
D/NATIVE-EPD( 1053): epd_reset_region: 0x20
D/EPD#ActivityResume( 1053): resetRegion 6
D/NATIVE-EPD( 1053): epd_reset_region: 0x40
D/EPD#ActivityResume( 1053): resetRegion 7
D/NATIVE-EPD( 1053): epd_reset_region: 0x80
D/EPD#ActivityResume( 1053): Disable EPD for 350ms!!!!!!!!
E/TC ( 1295): KPICollector: 1634499258078 ActivityManager background {"component":"com.home.nmyshkin.quicktiles/net.dinglisch.android.tasker.Kid"}
E/TC ( 1295): KPICollector: 1634499258111 ActivityManager foreground {"component":"com.gacode.relaunchx/.AllApplications"}
D/dalvikvm( 1645): GC freed 2790 objects / 148896 bytes in 111ms
D/dalvikvm( 1362): GC freed 15222 objects / 941720 bytes in 132ms
D/ReLaunchApp( 1362): --- onResume(AllApps)
D/dalvikvm( 1645): GC freed 1637 objects / 99640 bytes in 95ms
E/QuickTiles( 1645): 20.34.18#E: error: Read Line: no SD present.
D/SurfaceFlinger( 1053): Frame buffer posted; elapsed time = 31 msecs
I/PowerManagerService( 1053): setPowerState: mPowerState=0x3 newState=0x3 noChangeLights=false reason=1
D/SurfaceFlinger( 1053): Frame buffer posted; elapsed time = 11 msecs
D/dalvikvm( 1386): GC freed 8203 objects / 298784 bytes in 44ms
D/SurfaceFlinger( 1053): Frame buffer posted; elapsed time = 14 msecs
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f040000
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f020000
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f020000
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f040000
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f020000
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f020000
W/ResourceType( 1053): Resources don't contain package for resource number 0x7f060001
D/Searchables( 1053): Checking component ComponentInfo{com.google.android.providers.enhancedgooglesearch/com.google.android.providers.enhancedgooglesearch.Launcher}
D/SurfaceFlinger( 1053): Frame buffer posted; elapsed time = 11 msecs
D/dalvikvm( 1295): GC freed 1694 objects / 89152 bytes in 35ms

alexhorner said:
No luck after a few attempts inclusing a reboot I'm afraid. Attached is the logcat which complains of some failed link creations.
Click to expand...
Click to collapse
Sorry. I'll have to do it the hard way. I need to find out the correct syntax anyway for my other WIP.

nmyshkin said:
Sorry. I'll have to do it the hard way. I need to find out the correct syntax anyway for my other WIP.
Click to expand...
Click to collapse
No worries! Let me know if there is anything I can do to help

alexhorner said:
No worries! Let me know if there is anything I can do to help
Click to expand...
Click to collapse
Um....did you remember to copy the Qtiles folder (and contents) into /media from the sdcard (or the original zip)?

nmyshkin said:
Um....did you remember to copy the Qtiles folder (and contents) into /media from the sdcard (or the original zip)?
Click to expand...
Click to collapse
I did, and I also checked it's presence and contents via shell and ensured the permissions were loose

alexhorner said:
I did, and I also checked it's presence and contents via shell and ensured the permissions were loose
Click to expand...
Click to collapse
Huh. The apps works on my NSTG. And you did uninstall before the new install? Let me download what I posted and try that...

nmyshkin said:
Huh. The apps works on my NSTG. And you did uninstall before the new install? Let me download what I posted and try that...
Click to expand...
Click to collapse
I did indeed.
I uninstalled, moved the directory from SD to media using windows, checked with ADB shell that the files existed, and that they had loose permissions.
I then installed and attempted starting but no luck.
I also did several combinations of install, uninstall and reboots to ensure it wasn't a fluke

alexhorner said:
I did indeed.
I uninstalled, moved the directory from SD to media using windows, checked with ADB shell that the files existed, and that they had loose permissions.
I then installed and attempted starting but no luck.
I also did several combinations of install, uninstall and reboots to ensure it wasn't a fluke
Click to expand...
Click to collapse
I just downloaded what I posted and tried that. It also works.
MD5: 34c265a260da53ab9ac83d5ba154905a
CHMOD on the QTiles folder and contents = 775
Your logcat seems to be saying that the app never successfully installed. The files it is looking for in /data/data/com.home.nmyshkin.quicktiles are the xml configuration files normally installed by the apk package and one where variable values are stored as they change with operation and configuration. Something is definitely wrong. Did you ask RelaunchX to install this for you (which should invoke the stock package installer) or did you install via ADB, or.....?

nmyshkin said:
I just downloaded what I posted and tried that. It also works.
MD5: 34c265a260da53ab9ac83d5ba154905a
CHMOD on the QTiles folder and contents = 775
Your logcat seems to be saying that the app never successfully installed. The files it is looking for in /data/data/com.home.nmyshkin.quicktiles are the xml configuration files normally installed by the apk package and one where variable values are stored as they change with operation and configuration. Something is definitely wrong. Did you ask RelaunchX to install this for you (which should invoke the stock package installer) or did you install via ADB, or.....?
Click to expand...
Click to collapse
I have now fully uninstalled QuickTiles, recopied it over to my SD Card, recreated my QTiles directory in /media and installed using ReLaunchX - my usual install method is ADB, never have I installed anything using ReLaunchX before now.
Its working now. I guess yet another one of those unexplained issues... Quite annoying