yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] Riyal:
Depends on your definition of scratch. Obviously plastic is easily scratched than this device. But with plastic nomatter how deep the scratches are color won't be any different so it won't be that obvious. Unlike this device which uses a coating for color a scratch deep enough to scrape over the thickness of the coating would be obvious.
[One (M7) Q&A, Help & Troubleshooting] Barsky:
Ghost Armor skin now on the back of my black. There will be no scratching
[One (M7) Q&A, Help & Troubleshooting] ytzn:
screen is more easier to get scratches.

mine got 2 scratches in 2 days. All happened in my Chino cotton pocket.

i used the same way for SII and 2 years no scratches.

HTC one glass really sucks.
[One (M7) Q&A, Help & Troubleshooting] soul40k:
Absolutely nothing yet! No case,just screen cover
[One (M7) Q&A, Help & Troubleshooting] Tyler DeLarge:
Black?
[One (M7) Q&A, Help & Troubleshooting] soul40k:
I have the Silver one.
[One (M7) Q&A, Help & Troubleshooting] pcigre:
It has little to do with HTC. They use standard Gorilla Glass II.
[One (M7) Q&A, Help & Troubleshooting] rockson020:
I have a Black one, had it for around a month or so, dropped it twice with a case on, and also take it off the case and use it every now and then (for that orgasmic feeling on my palm :eek:)

No scratches at all so far, place it on different surfaces and put in different pants without a case :))
[One (M7) Q&A, Help & Troubleshooting] raghav2511:
I have a silver one and it got scratched rather quickly.. Ive been super careful but still.. Its kinda prominent scratch, on the back above the camera.. I guess it got scratched while sliding it in or out of my pocket.. Not a deal breaker though!
[One (M7) Q&A, Help & Troubleshooting] devilman1223:
Comparing with the white and black versions with both having scratch marks. I'll say the scratchings on the black one looks more prominent than the white.
[One (M7) Q&A, Help & Troubleshooting] slyevo:
Scratches

I purchased a Screen Knight full body protector from Ebay for £4.00 for my Silver HTC ONE and it's really good quality....
[T-Mobile Samsung Galaxy S 4] omf05:
I'm using cm10 and when someone send more then one PIC I got a slide show.

Any solution to it?
[T-Mobile Samsung Galaxy S 4] RMXO:
tell them to send one at a time instead of bunching them together maybe
[T-Mobile Samsung Galaxy S 4] omf05:
Yeah but that shouldn't happen. I get them fine with the Samsung stock message app.
[Galaxy S I9000 Q&A, Help & Troubleshooting] dandrake:
Title says it all.

Any help would be much appreciated.
[One (M7) Q&A, Help & Troubleshooting] aGoGo:
Hi everyone,

I'm having an issue updating my wife's rooted and unlocked HTC One.

I flashed stock recovery for the process to go smoothly but the update is always stuck at roughly 25%. I switch off the phone, it tries again and gets stuck again at 25% with a red mark.

I tried deleting the update and downloading it again through the GUI without luck.

I suspected 3rd party mods like the battery percentage hack, but it still didn't work after reverting it.

P.S. I also have an HTC One, had an issue updating because I had CWM, but the update worked like a charm when I flashed stock recovery.
[One (M7) Q&A, Help & Troubleshooting] aGoGo:
Any clues?
[One (M7) Q&A, Help & Troubleshooting] aGoGo:
Bump
[One (M7) Q&A, Help & Troubleshooting] x017in:
1. where are you flashing the update from? - is it a zip file or is it the one the pone received OTA?

2. Which recovery are you using?

3. Which Rom are you on?
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Dual Boot Exercises

Exercise I

An example current facts:

ROM: Samsung stock JB 4.1.2

Kernel: blackhawk single kernel

Recovery: PhilZ Touch prior version

Prerequisites step:

Update your kernel to blackhawk's NEXT kernel

Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery

Download CM latest nightly + GApps zip

~2GB free on internal storage

Dual boot step:

Reboot into recovery

Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it

Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!

Flash CM

Flash GApps zip

Reflash blackhawk's NEXT kernel

Reboot into secondary ROM - CyanogenMod!

It's always better if you make a backup before performing all above steps. Do it at your own risk!

Exercise II

An example current facts:

ROM: CM 10.1 latest nightly

Kernel: blackhawk single kernel

Recovery: PhilZ Touch prior version

Have Samsung stock 4.1.2 nandroid backup

Prerequisites step:

Update your kernel to blackhawk's NEXT kernel

Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery

Nandroid backup your current CM 10.1 ROM

~2GB free on internal storage. I am not sure, depend on your backup data size

CM 10.1 as 2nd ROM:

Reboot into recovery

Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it

Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!

Restore CM 10.1 nandroid backup

Format /cache, clean dalvik-cache

Reflash blackhawk's NEXT kernel

Reboot into secondary ROM - CyanogenMod!

Samsung 4.1.2 as 1st ROM:

Reboot into primary recovery, make sure you choose "Primary Recovery"! Make sure you really choose "Primary Recovery"!!

Restore Samsung stock 4.1.2 nandroid backup

Format /cache, clean dalvik-cache

Reflash blackhawk's NEXT kernel

Reboot into primary ROM - Samsung!

Do all above steps at your own risk!
[Galaxy Tab 2 7" Android Development] Fotonista:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
[Galaxy Tab 2 7" Android Development] dimfil:
There is no confusion at all...

Every file you need is in the first post: kernel, tool and Philz. Don't use anything else.

Read the examples. All information is in there...

I don't know about the differences between KK and Philz, but I don't care though... Philz is just great!

Many, many respects to ketut...

Big thanks for your efforts...
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
PhilZ Touch is a recovery image, NEXT kernel is a boot image, KK-Boot discontinued project.
[Galaxy Tab 2 7" Android Development] Vishesh:
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Yes. Fixed the problem when installed CM 10.1 directly as 2nd ROM. No wipe needed.
[Galaxy Tab 2 7" Android Development] dimfil:
Please let me ask a question here.

I have already asked in Philz's thread but no answer till now.

Can Philz restore backups made within cwm?

I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.

Please, ketut, any information on that?
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Compatible: http://xdaforums.com/showthread.php?t=2201860
[Galaxy Tab 2 7" Android Development] dimfil:
Great!

It's a lot of pages. I can't find it right away, but your answer is enough for me! So, they are compatible.

I will try and report if necessary.
[Galaxy Tab 2 7" Android Development] jaydyan:
This great work Ketut, thanks for giving us easy way to dual boot. Keep up the good job.
[Galaxy Tab 2 7" Android Development] distan7:
Ketut, congrats on your new achievement !

Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :

Thank you
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Same kernel, different ramdisk. Thanks for your support :good:
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
STOP PRESS: Update PhilZ Touch to 5.03.7 http://xdaforums.com/showpost.php?p=39935850&postcount=89!
[Galaxy Tab 2 7" Android Development] brolee93:
Oh good news my brother I am happy :D

Envoyé depuis mon GT-N7100 avec Tapatalk
[Galaxy Tab 2 7" Android Development] Andrev01:
Couple questions to ketut ;) Please try to answer me - noobie :D

1) I can flash this for single rom, yes? It should be better than previous version?

2) I can still turn Tab on, press volume down button to boot into CWM?

3) How to turn off the boot menu? (I think I don't need it)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
1. Yes as covered by Dual Boot FAQs. No.

2. Yes.

3. Can not be, maybe the next version. Reboot to recovery and bootloader may be removed for security reasons.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
First and second page updated!
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Thanks for your investigation but to tired to reply for now.
[Galaxy Tab 2 7" Android Development] arunmcops:
Humble Request

Can you please add following config flags in kernel for Ununtu support : :D

CONFIG_SYSVIPC=y CONFIG_NAMESPACES=y CONFIG_UTS_NS=y CONFIG_IPC_NS=y CONFIG_USER_NS=y CONFIG_PID_NS=y CONFIG_NET_NS=y CONFIG_DEVTMPFS=y CONFIG_DEVPTS_MULTIPLE_INSTANCES=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_FANOTIFY=y CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y CONFIG_SWAP=y # CONFIG_ANDROID_PARANOID_NETWORK is not set

Thanks in advance.. :good:
[Galaxy Tab 2 7" Android Development] tobbbie:
Small effect of 25% GPU OC? - just 6-10%?

I noticed that GPU benchmark does only benefit by

10% on 3D performance (e.g. 2235 -> 2472)

6% on the 2D performance (503 -> 534)

Despite the GPU OC is 1.25, so 25% from 307 to 384 MHz.

I have used Antutu selecting only the 2D and 3D tests and changing the value of /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc in a root shell cd on the path "/sys/devices/system/cpu/cpu0/cpufreq/" with either "echo 0 > gpu_oc" or "echo 1 > gpu_oc".

Results vary slightly but never get to the range of the GPU clock increase.

As screen display is also largely linked to memory performance, would there also be a need to tune memory access throughput here?
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
I will rebuild a kernel special for Ubuntu Touch, will ready when it's ready.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
A lucky day :cool:

Attached NEXT kernel Ubuntu Touch compatible (should be but untested), changed in:

- kernel

- ramdisk: fstab.espresso, fstab.espresso.2, init.espresso.rc, init.espresso.rc.2, init.rc

- installer to change build.prop: ro.sf.hwrotation=0 to set stagefright in landscape mode and debug.sf.nobootanimation=1 to disable boot animation

Untested but could still load standard CM 10.1 (Ubuntu Touch based on CyanogenMod CM 10.1). Test it, waiting for your feedback ASAP :D

EDIT:

And could still load Samsung stock ROM with wrong orientation camera app :laugh: You have to flash on both ROM for dual boot, incompatible kernel modules!

EDIT2:

Reupload to fix stock ROM orientation :p
[Galaxy Tab 2 7" Android Development] arunmcops:
Not booting. Black screen both cm n Ubuntu.
[Galaxy Tab 2 7" Android Development] Vishesh:
Ketut @ massive thanks to u sir for the 1.3 version.. I am with nooc with undervalued voltage values.. Found not a single issue.. So much less heat after undervalued voltages.. This is the perfect kernel in all respect.. BIG RESPECT.. outstanding work as always.. Amazing.. Hands down now:thumbup::thumbup::thumbup::thumbup:

¤ Help = Thanked ¤

Sent from Heaven
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Black screen because debug.sf.nobootanimation=1 but I can still use it to load CM 10.1 and stock Samsung ROM, for Ubuntu untested! Any dmesg output?

Send me [MENTION=2876940]Sympnotic[/MENTION] boot.img http://www.jheberg.net/captcha/FmqwVz-cm-10-1-20130514-unofficial-p3110-zip, my data plan remaining less than 20MB :(
[Galaxy Tab 2 7" Android Development] karaern:
generally seems your are right but somehow when using the tab with gpu 384 and cpu 1008, can pretty feel the smoothness becuse of the gpu increase and the eye acceptance is in a great importance. i think although the real values are low as you stated, that litle increase in gpu pushes the usage feeling forward, even the fact that increase in cpu makes better resdults (ofc we all know the heat issue especially on hot sunny days under the sun) (LOL sunny days in sweden LOL :laugh:)
[Galaxy Tab 2 7" Android Development] tobbbie:
Setting "echo 2 > gpu_oc" should (according to init.post_boot.sh) set GPU clock to 512MHz. The Antutu values are then for:

3D: 2517, so a small additional increase from 2472 - could even be within statistical variance with as low as 1.8%

2D: 576, a solid step up from 534 - 7.8%

So it seems that 2D benefits most from max. GPU OC (and would GUI "smoothness" not have to be attributed here?) - as much as 576 from 503 is 14.5% increase, despite the OC from 307 to 512 is 66%.

The total performance gain for 3D is 2517 from 2235 which is only 12.6% with the increased clock of 66% where with just 25% OC you get 10%.

Not sure about the price you have to pay with drain and heat on GPU OC, no clue either if there is something like a "governor" for GPU clock scaling.

I did some more tests with Nenamark 2.4 for values of gpu_oc:

0: 32.3 fps

1: 36.2 fps

2: 40.2 fps

Funny thing is that pushing the values to gpu_oc had no effect on performance if you stay in Nenamark. You need to leave the test, then push the values, then restart the test.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
In the next version, all files required by NEXT will be integrated in the boot.img (by using a different compression method). Single flash for both 1st and 2nd ROM! But this need a prerequisite conditions for stock/stock based ROM, a newer compatible PowerVR 3D binaries blob. This problem is still confusing me. Any idea?
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Ready for 1.4?

Changelog:

- Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM

- Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)

- Auto root (for stock)

- Auto busybox (for stock)

- Auto rotate (for both stock and CM) depend on ro.sf.hwrotation value, camera orientation fix included

- External sdcard and internal media swapper code integrated in boot.img (for stock as 1st ROM)

- Really override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor

- init script reworked (again), simplified

With so many changes, how if we called it NEXT 2.0?
[Galaxy Tab 2 7" Android Development] tobbbie:
Where is the confusion?

I appreciate to put all in the boot.img and so to avoid writing to each ROM's \system partition for modules - but does it not work for Stock ROM - or why are YOU confused?!

---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------

...overlap to my previous post, query to above:

Will stock ROMs with Busybox and already rooted be left as they are?

Will internal/external swapper only work if set so? I like to have the sdcard stay as media-only as the internal space is sufficient for me.

Can't I use an init script to set CPU settings (clock, voltage, governor) anymore? I observed I have to re-apply the settings once after a kernel update but then the script (created by System Tuner) worked.
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
No confusion at all :D People should follow prerequisites for any setup:

a) Flash latest blackhawk's NEXT kernel

b) Flash latest PhilZ Touch - blackhawk repack version - recovery

b) Atleast 90% battery left.

c) 2 GB free on internal SD.

d) Some spare time

And everything will be fine :D
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
1. NEXT will replace root, replace busybox

2. Depend on persist.customboot.sdcard value, external or internal

3. NEXT will override only CPU governor setting, remove all init.d scripts and reset /etc/init.post_boot.sh on update
[Galaxy Tab 2 7" Android Development] putti71:
Hi together, since I flashed version 1.3 the button for last used apps lost its function. After activating pie and deactivating it again, it works again.

Also Titanium Backup does not show the correct storage of ext Sd.

Is this a known problem? Can I do something about it?

Edit: titanium backup doesn't show any

ext-Sd with kernel 1.3

Sent from Telegraph
[Galaxy Tab 2 7" Android Development] Caldair:
Is there a way to enable logs when using these kernels? Or has it been ripped out completely?

Either way thanks for your continued impressive work on this project! 1.3 is running like a dream for me.

PS - Don't you ever sleep man?!?:laugh:
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Titanium Backup does not show external storage but we still can set the backup folder location to /storage/sdcard1. Thanks for your report.

Insomnia :laugh: You can load logger kernel module by editing /system/etc/init.d/02modules
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
- standalone nooc version, no longer as an addon for standard NEXT

- untested CRT off animation support
[Galaxy Tab 2 7" Android Development] antutu:
will be easier to set in stweaks app isn't it?

edit:

on Misc window
[Galaxy Tab 2 7" Android Development] superSUnoob:
agree!

I agree with this. the changes in gaming between kernel 2.1.3 and 2.1.5 are noticeable.
[Galaxy Tab 2 7" Android Development] karaern:
I can say the same thing. Without undervolting! Battery drain is just seen. With some undervolting maybe can have little bit difference. Seems 2.1.3 is better on that way.

Send by Galaxy Note 10.1 by TelephatyTalk.
[Galaxy Tab 2 7" Android Development] haseogu:
I think we can start benchmarking using better battery stat
[Galaxy Tab 2 7" Android Development] Andrev01:
2.1.5 kernel doesn't work with newest 20131030 4.3.1 PAC test build - I get bootloop after flashing kernel with blobs.

EDIT: Ok, it's rom fault...
[Galaxy Tab 2 7" Android Development] Linux:
What version work?

Inviato dal mio GT-P3110 con Tapatalk 2
[Galaxy Tab 2 7" Android Development] zeetherocker:
False alarm buddy... The kernel is just fine...!! You can use 2.1.5
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
Audit and SELinux slow down our device, consume more power?
[Galaxy Tab 2 7" Android Development] antutu:
Didn't know about slow down, coz didn't fell it that way

However power seems a bit consumed in 2.1.5
[Galaxy Tab 2 7" Android Development] DarkStryder:
Battery and performance do seem to take a impact. On cm10.2

sent from my xperia neo v
[Galaxy Tab 2 7" Android Development] nakbaliNe:
What i feel is battery drain pretty fast if we compare with next 2.1.3
[Galaxy Tab 2 7" Android Development] DarkStryder:
This is my battery life on 2.1.3! Playing modern combat 3 online for almost 3 hours, with brightness on full and CPU oc to 1.2 GHz!!

I call that brilliant!!
[Galaxy Tab 2 7" Android Development] Android-Andi:
Can someone test ChameleonOS 0.8 as 2nd Rom in Dualboot using NEXT Kernel 2.1.5? Because "Theme Manager" not working for me on 2nd Rom.

I tryed different Themes, 2nd Rom on CM/Cm based system.img and on stock/stockbased system.img ... nothing worked.

Maybe Kernel /2nd Rom related?

Logcat (E): http://pastebin.com/nbkKV7x7
[Galaxy Tab 2 7" Android Development] zeetherocker:
Just use a different theme chooser

You can the universal theme chooser..

Sorry forgot the name of the dev from whom I got those apks :( but all credits to him...
[Galaxy Tab 2 7" Android Development] haseogu:
I think i will revert to 2.1.3, i feel more battery drain in 2.1.5. I want to compare between that kernel
[Galaxy Tab 2 7" Android Development] Android-Andi:
Theme-Manager on ChameleonOS now working for me - but only if i install ChaOS as 1st Rom in Dual-Boot - it´s not working if ChaOS is 2nd Rom :( ...
[Galaxy Tab 2 7" Android Development] zeetherocker:
I have a p3100 so have to change the update script then flash and tell you the results... But before that did you try the apks I posted in the last page..??

Just copy those files to system\app\ and replace the files there
[Galaxy Tab 2 7" Android Development] Android-Andi:
i got it work now.

I haven´t tryed your apk´s :p but thanks :)

i posted a p3100 testbuild too but i don't know if it works.

All about here: http://xdaforums.com/showthread.php?t=2505798&page=2

Edit: Don´t know where is the problem when i flash the rom as 2nd rom. Works on 1st Rom. Maybe [MENTION=4021423]ketut.kumajaya[/MENTION] can have a look if there are different mount path or something else.... but restoring ChaOS Backup from 1st Rom as 2nd Rom made it work.
[Galaxy Tab 2 7" Android Development] tsatomas:
Maybe when you first flashed the next tool you configured secondary as stock,or something like this(hope you understand what I mean)
[Galaxy Tab 2 7" Android Development] ketut.kumajaya:
[MENTION=5153662]Android-Andi[/MENTION] I have no idea for now.

Someone asked me about efs partition backup. When I introduced STweaks support, a hidden feature added: backup efs filesystem contents and partition raw image, saved it as efs*.gz to /data/media. Better you copy both files somewhere outside your Tab :D
[Galaxy Tab 2 7" Android Development] Android-Andi:
[MENTION=4478859]tsatomas[/MENTION]:

i tried on both, new created system.img (one time for cm and one time for stock), on both not working.

If a CM-Based Rom is too big you need a Stock system.img ;)

[MENTION=4021423]ketut.kumajaya[/MENTION]

I think manual backup is the safest way, isn´t it?

But how to enable this feature?
[Galaxy Tab 2 7" Android Development] tsatomas:
Just an idea i had,you know better.

I had problem in PAC since long with theme chooser and I solved with the apk from zeetherocker :thumbup:
[Galaxy Tab 2 7" Android Development] Nasheich Xfiles:
hey dev, i have problems about installing rom at secondary rom

flashing slim rom, aospa, sshd v5 as secondary rom i didn't have any problems

but, when flashing mokee and hellfire rom, i have this problem, the hardware rotation goes wrong, i turn the tablet on landscape , but the effects of touch screen is portrait , and i turn again to portrait , the touchscreen effect is landscape,

i don't know if this connected with the kernel or just the rom itself
[Galaxy Tab 2 7" Android Development] Android-Andi:
I think you did somethin wrong :p

Start from the beginning will be the easyest way. Backup all important data and safe it on your PC.

Step 1: Cleanup

Boot Primary Recovery

Flash NEXT Tool

Delete System.img for 2nd Rom

Backup your current 1st Rom if you want

Step 2: Prepare 1st Rom

Make a Wipe Data Factory Reset (do both in PhilZ Touch)

Wipe Cache Partition

under "Advanced" do a "Wipe Dalvic Cache"

under "Mounts and Storage" do a "format /system"

Step 3: Setup 1st Rom

Flash 1st Rom

Flash Gapps

Flash blackhawk-next-kernel-2.1.5

Flash "proprietary-vendor-samsung.zip" (or "proprietary-vendor-samsung-4.1.x.zip" if it´s a Android 4.1 Rom)

Reboot to your Rom (!!!)

Step 4: Prepare 2nd Rom

Now reboot into recovery

flash NEXT Tool

Create 2nd system.img

Reboot Recovery

Step 5: Setup 2nd Rom

Boot into secondary Recovery

Flash 2nd Rom

Flash Gapps

Flash blackhawk-next-kernel-2.1.5

Flash "proprietary-vendor-samsung.zip" (or "proprietary-vendor-samsung-4.1.x.zip" if it´s a Android 4.1 Rom)

Reboot to your 2nd Rom

Be sure you did all steps i told you. Start from Step1. If your problem still exist report back.