yashsingh1/xdaforums huggingface dataset:
[HTC One X] vin4yak:
All AOSP Rom's consume more battery as compared to sense roms!

Try different roms from Android Development / Original Android Development and settle on which you find the best! ;)

PS: Rom comparing threads are not allowed here!
[HTC One X] B14ck7hund3r:
I experienced it the other way: HTC's services are draining as hell :silly:

Have you looked for wakelocks already? Many apps are preventing deep sleep of the CPU.
[HTC One X] vin4yak:
When I said sense roms, I meant custom sense roms... not the fully stock one! ;)

Sense + Rom cleaner + de-sense = great battery life! :)
[HTC One X] Busyb0x:
I'm a 40% at the end of the day with a simple usage (not heavy)

You can use a kernel with the smartmax governor and lower your maximum frequence. You can udervolt too, but in most of the case it will just keep your device cold while playing.
[HTC One X] pandaball:
Threads asking for the best ROM are not allowed. Closed.
[Galaxy S 4 Accessories] miahegypt:
Yesterday i bought the Spigen glass.tr screen protector

it's a dry protector and no wet solution needed

the biggest problem any one can had is the dust under the screen protector

anyway

i installed the protector after cleaning my phone screen very carefully and i was sure that there was no dust there

and of course after the installation there was some dust between the protector and the screen

i was very mad . it's a 30$ protector

i removed the protector and using some alcohol (the white one that u can find in any drug store )

i cleaned the protector

then i made sure that the protector stays wet with the alcohol and i applied it then used the squeegee to remove any small drops of alcohol between the screen and the protector

and now its perfect no dust and no bubbles at all

i wanted to share this with everyone having trouble applying his glass screen protector
[Galaxy S 4 Accessories] asolram:
thank you! mine is arriving next week I think. BTW, I think the post should go in the Q&A so more people can see the tip :) Thanks again!
[Galaxy S 4 Accessories] miahegypt:
i thought i posted it at Q&A

it's a mistake sorry

i hope one of the moderators can move it to Q&A
[Galaxy S 4 Accessories] charlesdickens:
The spigen glass series comes with an alcoholic cleaner. At least mine did.

Another tip would be that immediately after screen protector is placed, you can still adjust it by firmly nudging it in whatever direction you desire.

Likewise mine was perfect. Am really loving the glass feeling.
[Galaxy S 4 Accessories] saltmine:
Other tips for installing glass screen protection:

1. Turn on your shower with the highest water temperature possible, and let it run for about 3~5 minutes. Then, do the procedure in the bathroom. I find that this helps get rid of dust in the air.

2. First, go to a completely white screen, and remove all the dust you can see. This will get rid of dark colored dust particles.

3. Turn off the phone and remove remaining dust. Since the screen is black when it is off, this will get rid of lighter colored dust.

Glass screen protectors feel amazing. It's difficult to get rid of all the dust, but it's definitely worth it.
[Galaxy S 4 Accessories] drng69:
totally messed mine up.

On the first go, got a bit of dust under it - it was really noticeable - so decided to remove it and give it another wipe with the alcohol wipe. Didn't work so redid it several times.

Was about to throw the thing away when I read about someone using a lint roller. Used it on the underside of the protector and screen and not only did it remove the dust it "revived" the tackiness of the protector.

It is now (almost) perfect on my phone :o
[Galaxy S 4 Accessories] Shade08:
This. I did this when I got my Glas.TR for my iPhone, by far the easiest and best way I've found to install a screen protector.
[Galaxy S 4 Accessories] Khy50:
Just installed mine and there's a tiny white lint stuck underneath :mad:

I wouldn't mind it but it's created a little bubble, hope it goes away or I'll just have to live with it!

Update: took it off and sprayed some soap and water solution to clean it. Reapplied and squeezed out the water and haze, now its almost perfect :eek:
[Galaxy S 4 Accessories] Morimus:
thank you! helped me so much!
[Galaxy S 4 Accessories] SevenD2:
Like mentioned before:

1. Do it after taking a shower (this is make sure your hands are clean)

2. You can use sellotape (sticky tape) to make sure all dust is gone

3. Make sure you wipe it down with a microcloth (can be wet with water/alcohol) However some alcohol wipes will remove the oleophobic coating and cause smudging!)

Best way to clean screens is wet cloth and dry cloth
[Galaxy S 4 Accessories] trannhattan:
I've got bubbles at the edge for weeks. I wonder if I can lift the glass a lil bit to wipe the screen and re-attach it perfectly. If yes, what should I use to lift it? I know my fingernail can do...but I guess I can chip the edge by doing so :rolleyes:
[Galaxy S 4 Accessories] jetlitheone:
Yeah shower trick works. Usually have a perfect glass protector with not even one lint under it.
[Galaxy S 4 Accessories] mapobean:
you guys are all so funny. The best way is to use scotch tape to remove any particles under the protector both on it and on the phone.

1. clean the phone with alcohol swap

2. wipe with non lint cloth (most likely provided with protector)

3. start by separating the protector from backing slightly not removing it fully to avoid any debris and place top half on phone lining up properly.

4. work from top to bottom slowly with credit card or supplied squeegee working bubbles out.

5. if debris are noticed under protector do not try to lift with finger nail use scotch tape to lift the protector and slide another piece under the protector area to catch the debris.
[Galaxy S 4 Accessories] pachi72:
Omg I did the shower thing and I wet my phone completely..slipped into the bath. How I am suppose to put the screen while taking a shower...Omg..just joking..
[Galaxy S 4 Accessories] trannhattan:
Thanks for your advice. I applied the glass protector 2 weeks ago. I tried scotch tape for carton box but the tape wasn't that sticky to lift the protector. Have you got any further advice? Thanks
[Galaxy S 4 Accessories] mapobean:
I have always been able to lift with Scotch tape. Place the tape on a corner posing it firmly down on the protector leaving the tape extend as a tab. Lift slow just enough to seperate the two (screen protector from screen)
[Galaxy S 4 Accessories] mpetruzz:
I use the hinge method. You can go on YouTube and find videos. It really helps to get it on straight and helps eliminate bubbles.
[Galaxy S 4 Accessories] flu13:
I just looked up a video, and that is definitely sort of brilliant.
[Galaxy S 4 Accessories] Nyisles84:
I too used the shower trick, and for the most part, worked great. I needed a couple of attempts to line it up just perfectly however. Once I finally got it down, it looked fine. Next day I noticed a small speck of dust in the upper right corner. Just far enough away from the edges that would make lifiting it and using tape a little risky. We will see if my OCD can subside and Ill get used to it in a few days.
[Galaxy S 4 Accessories] trannhattan:
Thank you Mapobean. I tried it; however it only works on normal screen protector (the film one). I tried that from my friend's phone. Mine is glass screen protector and no way I can apply you useful tip. :crying:
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Dual Boot Exercises

http://xdaforums.com/showthread.php?t=2285366 post #4.
[Galaxy Tab 2 10.1" Android Development] Jeik:
Was waiting for this :victory:
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button :D or better my DTM button ;)

PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
[Galaxy Tab 2 10.1" Android Development] Jeik:
So this kernel boots 1 ROM over internal storage and second over SD card?
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Dual Boot FAQs #29.
[Galaxy Tab 2 10.1" Android Development] brolee93:
Ohhh good news i go to test thanks you rock

With 0.6 i can oc 1.35.

But now i have freez or reboot or black screen
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!:D
[Galaxy Tab 2 10.1" Android Development] shakatu:
Running smoothly for Zap Blaster. ;)
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:

Really? And all your init.d scripts removed by NEXT ;)
[Galaxy Tab 2 10.1" Android Development] shakatu:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.

After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind. ;)
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.

Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK. ;)
[Galaxy Tab 2 10.1" Android Development] behemot24:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us :cowboy:
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
For free ;) A lot of clicks to install NEXT package but why people missed to click my Thanks button :p

EDIT:

This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync :D
[Galaxy Tab 2 10.1" Android Development] Rahul721:
When i install this kernel on ZapBlaster the Video Player and Camera stops working :(
[Galaxy Tab 2 10.1" Android Development] shakatu:
Two apps I never use on my tablet, so I haven't tested them...
[Galaxy Tab 2 10.1" Android Development] brolee93:
yeah ok i see this .

can you add Stweaks support ?
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Damn! I forgot to change ducati heap size for P51xx, flash old ducati vendor blobs to fix hardware accelerated media!
[Galaxy Tab 2 10.1" Android Development] kenundrem:
Its all good looking forward to the fix...newest kernel runs great on 311x platform with extra ram
[Galaxy Tab 2 10.1" Android Development] xVermicide:
what about the ram size? i still have 764
[Galaxy Tab 2 10.1" Android Development] sjsharksfan420:
After flashing the old blobs, do we need to refresh a fixed vendor blob file?

What issue does incorrect heap size cause, I would like to see if I am effected

sj
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
P51xx still can not utilize the new ducati firmware (and 815.8MB RAM size) because today is family day :D If you flash the new ducati blobs, camera, gallery, video, etc which need hardware accelerated media will fail to work!
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
Family first KK! :) GOOD MAN!
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
In a trip but my laptop always with me :D

Just reupload 1.8.3 with fixed ducati memory heap, reflash it and then directly flash the new ducati blobs. Please check your memory size and camera.
[Galaxy Tab 2 10.1" Android Development] kenundrem:
Working better ram now at 805mb thank you!
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
KK, your wife and kids were probably shaking their heads at you the whole time! :p
[Galaxy Tab 2 10.1" Android Development] XpLoDWilD:
So I bet you know that MMC CAP ERASE was the source of hardbricks (eMMC dying) on many Samsung device? Wipe data, boom dead.
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Ha..ha..ha... Four kids! So, the best time for me is midnight :laugh:
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
In the previous version, my kernel for P31xx and P51xx always with MMC_CAP_ERASE disabled but no one experience MMC hardbrick by using CM kernel with MMC_CAP_ERASE enable, so I reenabled it.

EDIT: Tab 2 family (OMAP4430 platform) has a separated partition/kernel for recovery and normal boot. For P31xx, I still used a kernel with MMC_CAP_ERASE disabled in my repack version of PhilZ Touch recovery. In PhilZ and all CWM based recovery for Tab 2, formatting /data not actually format it but just a "rm -rf" command excluding /data/media .
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
Ok, so according to this instructions I am supposed:

1. To upgrade to 1.8.3

2. Flash the new vendor blobs zip

3. Flash/switch to another kernel (1.6.3 for example)

4. Flash the old vendor blobs zip

5. Then flash a different kernel or the previous one I had, that being 1.8.3?

I did exactly the steps I just described and CM10.2 jb4.3 works with no major issues other than having to gain root again using superSU. Camera works, gallery works.

am I doing it wrong? Can someone share their thoughts on how it should be done? I'm only doubting my ability to understand bcz i doesn't make sense to me why I would flash new vendor blobs and then go back to old vendor blobs, unless both blobs are needed and one does not override the other one, and and they just need to be flashed in that order? Any help will be appreciated
[Galaxy Tab 2 10.1" Android Development] sjsharksfan420:
You're the man! Thank you sir!! Hope you're having a great time with the family!

sj

Sent from my PimpedOut® D710 on ReVolt-JB using Tap@Talk Pro

---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------

I think the old blobs were the ones that had the correction needed.. But I can't explain why we would need to flash old blobs then new again..

Edit: I just flashed the new fixed kernel and looks like it might break sdcard mounts..

sj

Sent from my PimpedOut® D710 on ReVolt-JB using Tap@Talk Pro
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
Thanks, but im more worried about the order in which they need to be flashed. From what i gather, we are to flash the NEW blobs first, then the OLD one according to his post?
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
The fixed version of 1.8.3 need the new ducati vendor blobs.

This kernel work on 4 types of ROM, please inform me your ROM version.

- The new fixed version of 1.8.3 need the new ducati vendor blobs

- The older version need the old ducati vendor blobs
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Still waiting for feedback and let's see what can I do. Always inform your ROM version and don't quote the whole OP.
[Galaxy Tab 2 10.1" Android Development] xVermicide:
cm10.2 2013-8-07 unofficial p5110

after flashing cm10.2 and 4.3 gapps, i flash the 1.8.3 kernel and the new blobs and boot.

i get 804mb instead of 764 i believe it was, or 746?

however, at 1480 max oc, the performance is slightly worse than stock kernel 1ghz.

i'll flash stock kernel to check it out.
[Galaxy Tab 2 10.1" Android Development] sjsharksfan420:
The way it worked for me was I flashed new kernel first, then old blobs then i was able to get back to 1.6.3.

sj

---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------

My current test was for the latest build of PACman, I am testing to see if sdcards mounts are not working.. I will advise

Update: new kernel works perfect for PACman. :)

sj
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
The fixed 1.8.3 freeing ~40MB RAM space, please inform me about camera, gallery, and hardware accelerated video playback.

OMAP4 platform has a mechanism to slow down CPU speed if CPU temperature too hot. Maybe 1.48GHz too high for your device.

Waiting for your report.
[Galaxy Tab 2 10.1" Android Development] sjsharksfan420:
Hi KK, I just finished up, new kernel up and running on PACman, mounts are perfect!! Gallery and camera are both working perfect as well.. Netflix, youtube, hulu, directTV, all running very smooth.. I will run my tests for CM10.2 as soon as I have time and can restore my backup

sj

Sent from my PimpedOut® D710 on ReVolt-JB using Tap@Talk Pro
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
Flashed the new blobs, then the 1.8.3 kernel and after reboot into my primary ROM it would not go past the initial black screen. I was only able to boot after flashing the old blobs and then the kernel 1.8.3. See screenshot for my ROM details.

Also using cm 10.2 for secondary ROM and will not boot either unless doing the above. I'm using a 5113
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
1.8.3 kernel version should be 3.0.41 :confused:
[Galaxy Tab 2 10.1" Android Development] sjsharksfan420:
Hi KK, I just finished up, new kernel up and running on PACman, mounts are perfect!! Gallery and camera are both working perfect as well.. Netflix, youtube, hulu, directTV, all running very smooth.. I will run my tests for CM10.2 as soon as I have time and can restore my backup..

Update: tested v1.8.3 on the 8/7 build of CM10.2 (4.3) and everything is perfect, sdcard mounts good, camera/gallery are good, all video streaming apps work perfect. :)

Great job KK!! :beer::beer::beer::D:sly::beer::beer::beer::beer::beer::beer::thumbup:

sj

Sent from my PimpedOut® D710 on ReVolt-JB using Tap@Talk Pro
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
Sorry , wrong screenshot.
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Please upload a screenshot to prove your claim :D One just like [MENTION=2232273]cubandanger05[/MENTION] shot ;)
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Please redownload 1.8.3 (fixed version, dated Aug 10). Flash the kernel first and then the new ducati blobs. Waiting for your report.
[Galaxy Tab 2 10.1" Android Development] sjsharksfan420:
I will as soon as my backup completes. I will post one from CM10.2 & I will restore my PACman backup and post one from that one too

CM10.2:

extSD mounts:

PACman:

sj
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
Working now thanks
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
Also working with cm10.2
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Good :good: Please check camera, gallery, hardware accelerated video playback.
[Galaxy Tab 2 10.1" Android Development] cubandanger05:
All good :thumbup:
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Post #2 updated, changelog info. Please read this kernel thread at P31xx sub forum for complete history behind :D

Changelog:

10/08/2013 1.6.3 -> 1.8.3

:

Initial upcoming Samsung 4.2.2 support

Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support

Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!

Updated to upstream Linux kernel 3.0.41 (incremental patch)

The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel

zram switched to zsmalloc, zram optimized for Android disabled

XBox 360 USB controller with BigX LED support enabled (by [MENTION=4959889]iks8[/MENTION] request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
This is my take with it. Focal was also giving me problems on stock CM 10.2 kernel as well.
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
What about camera app?
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
Camera app works great KK, sorry should've mentioned it! :thumbup:
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Out of Thanks for today, thanks for your feedback.
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
KK, thanks for all your extra time and effort, I know the kids and wife didn't really benefit from all this like we did, unless it made you feel so good you did something extra nice for the family that is! Sounds like icecream could be a good idea ? :D
[Galaxy Tab 2 10.1" Android Development] xVermicide:
gallery is performing super fast, so is camera. and using mx player with hw+ codec, high resolution videos are playing smoothly and seeking is instantaneous in every video no matter how large the file.

this is awesome

edit;

ho. lee. sheeeeit. using quickpic with hardware rendering enabled, I'm able to go into a folder of 470 pictures and about 40 videos, and instantly all the images are thumbnailed and I can use the thumb scroller to smoothly move up and down the entire folder and it doesn't skip a frame or freeze up while it loads more thumbnails. I've never felt performance like that with this tablet before.

-Sent from my Galaxy Tab 2 10.1 [P5113] using Tapatalk 4
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
A good idea, a good support :laugh:

The new ducati firmware for multimedia co-prosessor taken from Samsung 4.2.2 leaked ROM for P3100. This ROM using a different kernel source (still 3.0.31 kernel :( ) but I managed to load the ducati firmware with a small change in kernel :D I also managed to boot Samsung 4.2.2 using my own kernel. This kernel ready for upcoming Samsung 4.2.2 for P5100 :D Samsung employees, don't be lazy! Hurry, my kernel ready for your ROM :laugh:
[Galaxy Tab 2 10.1" Android Development] ironmaskusa:
We love ya KK, just don't go to work for Samsung because then we would never get any work from you over here at XDA! :p
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Ha..ha... I also maintain two Samsung turbo compressors. A very big machine operated by a PLC and 7" LCD touchscreen. OT :p
[Galaxy Tab 2 10.1" Android Development] brolee93:
thanks for this big update i ddl and go to test with my latest rom thanks for all my bro your are the best
[Galaxy Tab 2 10.1" Android Development] ketut.kumajaya:
Post #3 updated!

Dual Boot FAQs

Adapted from droidphile's "Dual Boot FAQs" with permission.

1. "Why would I wanna dual-boot?"

A. You don't have to.

Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.

Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.

And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.

2. "What if I don't need dual booting?"

A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.

3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"

A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.