Database Develop

Testing Tables, please ignore

Tryintg to figure out how to add tables to posts.
So|Exactly|How
does|this|new
fangled | thing | work
and |just |what
is | it | good |
for | |
Ok, so the patch for tables is not installed.

Fail.

Not a fail to make the attempt, I have tried this myself as I would like to be able to make columns in posts too. I guess there must be some reason the admins haven't put the patch on, although they might look into it if asked. This thread should be in the About xda-developers.com forum to get their notice, or asked in this thread. (requests) From the Users to the Mods & Admins

Yes, the only option I've found so far is using preformatted text, and wrapping it in code tags. That gives an ugly font, etc. Even then you have to take into account the font. The editing box has a proportional font, and the display is fixed width. The third column shows what can happen.
Code:
So Exactly How
does this new
fangled thing work
and just what
is it good
for

sysadmn said:
Yes, the only option I've found so far is using preformatted text, and wrapping it in code tags. That gives an ugly font, etc. Even then you have to take into account the font. The editing box has a proportional font, and the display is fixed width. The third column shows what can happen.
Code:
So Exactly How
does this new
fangled thing work
and just what
is it good
for
Click to expand...
Click to collapse
Another way to do it is using a smart trick from Lesicnik1:
A1[COLOR="White"]---------------------[/COLOR][COLOR="Red"]A2[/COLOR][COLOR="White"]---------------------[/COLOR]A3
B1[COLOR="White"]---------------------[/COLOR][COLOR="Red"]B2[/COLOR][COLOR="White"]---------------------[/COLOR]B3
C1[COLOR="White"] --------------------[/COLOR][COLOR="Red"]C2[/COLOR][COLOR="White"]---------------------[/COLOR]C3
A1---------------------A2---------------------A3
B1---------------------B2---------------------B3
C1 --------------------C2---------------------C3

Homescreen icons always redraws

hi all
my Xperia TX 4.3 maybe have problem all icon at main home screen always redraw when i run an app then quit by press Home button, i add
this code ro.HOME_APP_ADJ=1 to build.prop but didn't solve my problem. please help me. thanks.

ok, i've got it. check Disable HW overlays in develop options and no more redraw icons

devilmaycry2020 said:
ok, i've got it. check Disable HW overlays in develop options and no more redraw icons
Click to expand...
Click to collapse
http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/
I recommend reading part 1 also, but just to summarize:
ro.HOME_APP_ADJ – BUSTED
This property is supposed to “keep the launcher in memory” under the assumption that it would somehow make it faster. Unfortunately, this is a leftover Gingerbread property that no longer functions in ICS.
Gingerbread:
Code:
// These values are set in system/rootdir/init.rc on startup.
...
HOME_APP_ADJ = getIntProp("ro.HOME_APP_ADJ", true);
ICS:
Code:
static final int HOME_APP_ADJ = 6;
Google likely removed the ability to configure this value via a build.prop setting in ICS so that users could not set inappropriate values here.
SUMMARY
As we have seen many times already, there are no “magic properties” that you can set that will simply make your phone [insert desired superlative]. That is not to say that all build.prop settings are pointless. Some can actually provide some useful functionality. The key is not to blindly throw a slew of “tweaks” into your build.prop, but to carefully consider each one and know what they do (if anything) before using them.
That’s it for part two. Let me know what build.prop settings you want to see in part three!
Click to expand...
Click to collapse
If you really want to keep your launcher in memory, you can use App Settings (xposed module); I know for a fact it works because I use it, or you can even do it yourself with a script such as:
#!/system/bin/sh
sleep 60
PPID=$(pidof com.whatsapp)
echo "-17" > /proc/$PPID/oom_adj
Click to expand...
Click to collapse
To lower the oom value of the app you want to avoid getting killed off by android.

[Dev][Request] Simple Test needed - Help us get Steadyshot on Z1

Hold your horses, this requires a patched kernel which allows the lower frequencies. I'll upload one later today.
I added a modified kernel which allows underclocking. It's untested as I do not have a Z2. Do not flash this unless you know what you're doing. It might set your hair on fire or break your precious, expensive Z2.
--
Hey guys,
I'm one of the devs who ported 4k and 120fps to the Z1, along with @Riyal and @olokos. There is one missing piece: Steadyshot for 4k recording.
I personally believe we will never get Steadyshot+4k on the Z1 because the hardware is not capable enough. The S801 in the Z2 has a much faster Video Post-Processor (PP) which is used for software image stabilization. It is clocked up to 465MHz while the S800 in the Z1 goes up to 320MHz max.
I'm looking for someone to _underclock_ their post processor to 320MHz. If 4k+steadyshot works, this means my theory is wrong. If your viewfinder freezes, then my theory is right and we the hardware is just not capable (without a serious overclock).
Messing with your hardware can always break something. I tried _over_clocking my Z1 to 465MHz, but that didn't work. Underclocking should be reasonably safe. But please, if you can't assess the risk of this experiment, or if you are not an experienced leet haxx0r, PLEASE LEAVE THE THREAD. DO NOT POST ANY IRRELEVANT CRAP.
What I need
Experienced User/Developer - someone who can fix their device if something goes wrong
Five Minutes of your time
You should have a Z2
You should have an adb root shell handy
You should have 1-2GB of free space on internal storage for the recording
What I want you to do
Open 4k camera, enable Steadyshot, Hit record
Recording should work properly, viewfinder should display video​
Now we verify the current clock of the PP. This should be 465MHz. In your adb shell, enter the following:
Code:
cat /d/clk/camss_vfe_cpp_clk/rate
Now we lower the clock the 320MHZ, the maximum PP clock of the S800:
Code:
echo 320000000 > /d/clk/camss_vfe_cpp_clk/rate
Now look at the phone (while recording!)
I expect your viewfinder to be frozen, recording will be corrupt. PLEASE REPORT YOUR FINDING.​
In your shell, check dmesg - you will probably see some overflow errors.
To sum the experiment once more:
We bring the clock frequency of the S801 down to the level of the S800 to figure out if it's the higher clock frequency which enables software image stabilization in the Z2. The outcome that we measure is whether lowering the clock frequency stops the viewfinder or not.

i started recording all ok with steadyshot and all that jazz
lagalaga said:
[*]Now we verify the current clock of the PP. This should be 465MHz. In your adb shell, enter the following:
Code:
cat /d/clk/camss_vfe_cpp_clk/rate
[/LIST]
Click to expand...
Click to collapse
This works
lagalaga said:
Now we lower the clock the 320MHZ, the maximum PP clock of the S800:
Code:
echo 320000000 > /d/clk/camss_vfe_cpp_clk/rate
Click to expand...
Click to collapse
This doesnt error out
and i noticed no change in the viewfinder so i cated again and the freq had not changed.
Code:
1|[email protected]:/ # cat /d/clk/camss_vfe_cpp_clk/rate
cat /d/clk/camss_vfe_cpp_clk/rate
465000000
[email protected]:/ # echo 320000000 > /d/clk/camss_vfe_cpp_clk/rate
echo 320000000 > /d/clk/camss_vfe_cpp_clk/rate
1|[email protected]:/ # cat /d/clk/camss_vfe_cpp_clk/rate
cat /d/clk/camss_vfe_cpp_clk/rate
465000000
so i checks dmesg
Code:
<6>[440814.479250] dhd_set_suspend: Remove extra suspend setting
<6>[440814.492694] mdss_dsi_panel_on: ctrl=f628e010 ndx=0
<6>[440814.718957] max1187x 8-0048: set_resume_mode
<3>[440830.477228] clk_set_rate(camss_vfe_cpp_clk, 320000000) failed (-22)
im on .69 with stock kernel just rooted.
pvy.

Thank you, I think we need a kernel mod - The Z2 kernel is fixed at 465 MHz. Thanks @eViLSt3ve

lagalaga said:
Thank you, I think we need a kernel mod - The Z2 kernel is fixed at 465 MHz. Thanks @eViLSt3ve
Click to expand...
Click to collapse
prety sure @DooMLoRD's kernel has it but i am not sure if the version for .69 does. i'll have a look in a bit
pvy

This is the relevant code in arch/arm/mach-msm/clock-8974.c:
Code:
static struct clk_freq_tbl ftbl_camss_vfe_cpp_clk[] = {
#if !defined(CONFIG_SONY_CAM_V4L2)
F_MM(150000000, gpll0, 4, 0, 0),
F_MM(266670000, mmpll0, 3, 0, 0),
F_MM(320000000, mmpll0, 2.5, 0, 0),
F_MM(465000000, mmpll3, 2, 0, 0),
#else
F_MM(465000000, mmpll3, 2, 0, 0),
#endif
F_END
};
The #ifs etc must be removed - and then the last F_MM line

Kernel uploaded in OP.

lagalaga said:
Kernel uploaded in OP.
Click to expand...
Click to collapse
what sources is it from? ( what stock revision )

pvyParts said:
what sources is it from? ( what stock revision )
Click to expand...
Click to collapse
402!

lagalaga said:
402!
Click to expand...
Click to collapse
OK ta I can't flash that idowngraded to play with some stuff will be re-upgrading this week if no one else does I'll check it then
Sent via my wireless blackbox

pvyParts said:
OK ta I can't flash that idowngraded to play with some stuff will be re-upgrading this week if no one else does I'll check it then
Sent via my wireless blackbox
Click to expand...
Click to collapse
Thanks I can't build another kernel right now, I only have a 120G SSD and it's full of stuff I need

Yeah no worries. I'm of to bed, then work, then Ciro, xD then I was gonna flash my update again. And I'll try it then.
Sent via my wireless blackbox

could doomkernel be used for downclock also? anyone else tested it on z2?

Bump

Bump

[MOD] NFC Screen OFF (.206)

Hello,
Here I leave the NfcNci.apk modded in order to work even when the device is locked and screen is OFF
You don't have to worry about battery life, I have already tested it and it does not have any appreciable impact on it
IT MAY (SHOULD?) WORK WITH SONY XPERIA X TOO, though is untested (post here if it works for you)
Installation:
Download attached NfcNci.apk file
Overwrite it into /system/app/NfcNci.apk and chmod 0644 it
Delete /system/app/NfcNci/oat folder
Reboot or "svc power reboot" through ADB
Done
Click to expand...
Click to collapse
TESTED ON: Sony Xperia X Compact 34.2.A.2.69
UDPATE (22-08-2017):
-Now compatible with FTF build .206 (download NfcNci(.206).apk and rename it to NfcNci.apk)
If you are interested about modding it for your device, you can see what I did here:
https://github.com/bamsbamx/NFCScreenOFF

Is it possible to have a white list of what tag will be processed when the screen is off?

trewelu said:
Is it possible to have a white list of what tag will be processed when the screen is off?
Click to expand...
Click to collapse
I think there is no easy way to mod the system NFC APK to make it work like what you say. Instead, it would be possible to create an app that handles all NFC tags and override the functionality of those tags which aren't in the whitelist

Hi
Thanks for the mod.
I'm wondering if you've included support of taglost detection ?
And maybe : it is hard to have a mod for a detection on lock screen instead of "screen off" ?
For me a "screen off" detection is too annoying since my phone can be in contact with some NFC cards in my pocket/bag.
I was able to do it for android 5.x on my Z3 compact but it's a long time ago.. can't remember what I did back then

Le_Poilu said:
Hi
Thanks for the mod.
I'm wondering if you've included support of taglost detection ?
And maybe : it is hard to have a mod for a detection on lock screen instead of "screen off" ?
For me a "screen off" detection is too annoying since my phone can be in contact with some NFC cards in my pocket/bag.
I was able to do it for android 5.x on my Z3 compact but it's a long time ago.. can't remember what I did back then
Click to expand...
Click to collapse
Hi,
I dont know what do you mean by "taglost detection", but this mod is based on the SONY's stock rom NFC app, so it should be included if it's also in the original app.
I think adding just on-lock-screen detection should be hard, you can follow the quick guide I wrote here: https://github.com/bamsbamx/NFCScreenOFF/blob/master/README.md
But keep in mind if you want just lock screen you should set .field static final NFC_POLLING_MODE:I = 0x2 instead of .field static final NFC_POLLING_MODE:I = 0x1
I cant test by myself that way because I am using AOSP rom right now... But will help you if you need

bamsbamx said:
Hi,
I dont know what do you mean by "taglost detection", but this mod is based on the SONY's stock rom NFC app, so it should be included if it's also in the original app.
Click to expand...
Click to collapse
By default there's no tag lost detection.
The tag_lost detection allow to trigger action when the tag is removed, not only when the phone scan the tag.
For ex you can use this to set the phone in a particular state (commonly: car mode, desk mode, etc) while the tag is detected. When the tag is removed, you use the tag_lost trigger to get off the mode, or trigger any other action (with tasker for ex)
I just got my X compact, and still not rooted yep. At this time I'm trying to use it without root... but the nfc mod my push me to do it
If so I'll take a look at this and post here

Please support 34.3.A.0.238 ?
On my phone, introducing this will cause nfc to disappear.

Question SetEdit value

Hello, I downloaded SetEdit on my phone today and I have questions about 2 values
- The first one is deviceLevelList, I know it enables blur effects but for some reason, setting "g:1" to 3 doesn't enable the blur effect and I find the gray background quite annoying
- The second one is a value I modified by accident, it's "misettings.support.repost", I don't know what it does so I set it back to 1 but if anyone knows what it does, I would love to know!
Thanks in advance