yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Asmodat:
I know why it is not working for you (I forgotten to repost): That's because in my case extending the pen also stabilised it - thow it stopped going crazy.

Then i also noticed, that bending ... rather pressing the tablet in specific places fired the detatched message.

ANY WAY FOLLOWING SOLUTION IS 100% WORKING:

- The issue is to much loose in pen holder, so if the pen is not stabilized, even slightly move of pen or bend of tablet can detatch or reattach it.

TO FIX IT: Take the 2cm / 1inch piece of narrow transparent tape, then stick it below the silver head of pen.

I has to help, however it must be peace of tape of certain length not to long (you will not fit the pen in the holder), not to short.(it will not stabilise it).

Now I can do whatever I wont wyth my tablet, bent, press, etc - for me problem is solved, although i beleave some software code could easly fix it too, or disable the stupid feature.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] earthtk:
Same problem.. The solution for me was to go to the service centre to get a new pen.:p
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] nonukez:
I'm having the same problem here. For me, it seems like this problem happened over time. I had this device for a month, and it's only the past week that I've had this problem. The slot for the pen seems to have loosened, and the pen slides out ever so slightly (still secure), but enough to be detected. It's very annoying, as I have a case with the sleep cover function, and the "pen detached" notification turns the screen on regardless of it being turned off from the cover. Battery drain while in bag FTL.

I'm wondering if there's a way to disable the feature altogether. I'm rooted, so I don't mind a rooted solution. I'd rather this than having to carry the pen separately, as the hole in the tablet will still be useful this way.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] notebooko:
Had the tablet for 2 days and everything is perfect. There is 1 problem though, the S-Pen isn't loose, but when it's moved outwards like <1mm then the tablet will turn on because it thinks the S-Pen is detached. I compared this to my defective screen tablet that I have not yet returned and that one does not activate when moved even a millimeter outwards. I will be returning both these tablets because it will most likely get worse over time and get looser in the slot. I'm really disappointed at the moment and hoping the next replacement will be my last. If not I may just have to go with the iPad Air and get one of the expensive styluses for more precise input.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dr.m0x:
Even those expensive iPad styli aren't even close to the s pen experience.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] notebooko:
I agree, and I probably will not end up getting an iPad. I'm just kind of angry at Samsung at the moment and just saying things that'll make me feel better. Meanwhile, let's see how many returns it takes for me to get a tablet with no big problems. :silly:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] colour1100:
I had the same issue. So I went to service station. they proposed to change s pen and the whole s pen dock which is attached to the screen Pannel. Now will be getting the replacements in 3 days. screen Pannel. According to them the s pen dock is attached to the screen Pannel. Now will be getting the replacements in 3 days. Hoping for the best. my S pen is very loose. It wasant so it was just loose on one side but after they opened my Note it became too loose. So its better to get a replacement.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] cici:
Exactly the same thing with my P605. Went to Samsung service on Friday, January 10, and in less than one hour the problem was fixed, the s-pen's detection distance becoming ~2 mm. The s-pen position in silo doesn't matter (if it is introduced with the button toward the screen or to the back camera). I've tested also the s-pen with the sensitive tip removed, it keeps the same distance of 2 mm with or without tip. I've asked the lady from the desk for the technician that fixed my tablet to talk with him just 1 min to ask him what he did, she said that is forbidden. Than I asked her to tell me how the tablet was fixed, she said that it was opened and the sensor was repositioned in the right place. I looked carefully with a magnifier if there are traces on the case, it looks like the case wasn't touched. By the way, they didn't specify anything on my guarantee certificate, and they didn't release to me any written paper concerning this problem and how they fixed it. My feeling is that the s-pen sensor's position was recalibrated digitally, using a hidden menu. Testing my s-pen in the demo P605 tablet from the showroom (inside the same Samsung service building), the tolerance was ~1.5 mm. Hopefully this information will be useful to anybody experiencing this annoying thing.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] HumanCaviar:
I would love to see this as well. Maybe there's something like turning off home button wake in /system/usr/keylayout/gpio-keys.kl ? Like OP, the issue is improved greatly when the S-Pen button is facing toward the back of the device.

BTW, where the hell is the ROM development on this device. I haven't seen a ghost town like this on a Samsung device since the Behold II.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] x3202:
warrantary worked

now i had to sent my device to the support for some reasons as well and they managed to fix the problem. they didn't replace the s pen and it still feels quite loose in the silo but there are no detached messages anymore!

they had to open the back because they changed the battery, so i can't say if they fixed the sensor or if it was a software fix
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] filimonic:
I have fixed it by myself (just because I had no warranty for some reasons)

It is hardware problem and can not be fixed by firmware, so, if you want, go to service.

http://xdaforums.com/showthread.php?t=2619474
[Samsung Galaxy Ace Plus S7500] Tank9:
Nobody is responsible in your actions with your phone! Everything you do at your own risk!

Hello everyone!I am looking for developers, and idealists in the care and creating a full flash based-based CyanogenMod 7.x!

I think that CM7.x is the most stable firmware for our phone, all other versions (CM9-CM11), they are not suitable for everyday use!

Link to my profile github.com
[Samsung Galaxy Ace Plus S7500] Tank9:
Reserved
[Samsung Galaxy Ace Plus S7500] coolfzk:
couldn't agree with you more,how I wish I could be a devoleper!but cm7 seems too old,I prefer to cm9
[Samsung Galaxy Ace Plus S7500] akki809:
If u have and time and really wanna be developer of ace plus.. Head towards kernel 3.x.
[Samsung Galaxy Ace Plus S7500] coolfzk:
you misunderstand me,in fact,I konw little about how to develop it,I interested in it,but I don't have a computer now
[Samsung Galaxy Ace Plus S7500] loxdegio:
If you need help I'm working on it, but I still find some boot problems
[Samsung Galaxy Ace Plus S7500] khaledreno:
i think it's the worst idea

cm 7 is bassed on android 4.0.4 can't support new games and programes and aslo cm themes and when we port it (IF WE )

it will be FULL of bugs and the kernal will be 3.x the same as we porting it

so let's port cm 10.2 bassed on 4.3 will unlock new drivers and performance improved and other things

so waiting is the best solution for cm 10.2 while we porting it , cm 10.1.2 will finshed of bugs :D
[Samsung Galaxy Ace Plus S7500] Tank9:
CM 7 is Android 2.3.7 but it does not 4.0.4! Essentially all of this is true, but, for our better devaysa SM7 will not, other versions SM9-CM11 is not for the weak of our devices!
[Samsung Galaxy Ace Plus S7500] blinqipa:
Please!

Guys , please , tell some respect to the [DEVELOPER] not because he did something , but he is working on , to bring the best performance .

He's working on this , he had chosen this ROM , surely there's a reason behind that!

Tell some respect , rather than SPAMMING , contribute :eek:

I'm with CM7.x , if you port it , that'd be great !

Thanks :highfive:
[Samsung Galaxy Ace Plus S7500] omarilzz:
actually its based on 2.3.7

cm9 is the one which is based on 4.0.4

and i m agreeing with cm7 port cause for some reasons GB IS WAY BETTER WITH SOME GAMES So i use it a lot so i support him
[Sony Xperia Miro, Tipo (Dual), J, E] Completely Absurd:
Hi guys,

I am using sony xperia tipo ST21i that is rooted. And I am planning to unlock my bootloader to install cm 10 from fxp. I want a piece of clarification. Does unlocking bootloader revoke the root access? In other words, does it unroot my phone? Or the root access stays?

Thanks in advance!:D:)
[Sony Xperia Miro, Tipo (Dual), J, E] sham4u2sam:
Unlocking bootloader will not unroot ur mobile.Before unlocking bootloader make a back up of ur TA.Search in xda abt it :good:
[Sony Xperia Miro, Tipo (Dual), J, E] Completely Absurd:
I didn't know we could back up DRM keys. Thanks a million! :good: :highfive:
[Sony Xperia Miro, Tipo (Dual), J, E] msxisalive:
rooted but not unlockable bootloader

I'm in a very similar situation: I have rooted my mother's ST21i but bootloader is locked (and pressing *#*#SERVICE#*#* it says it's not unlockable).

Was you able to unlock bootloader? How?

Thank you very much in advance.
[Captivate General] ajeesh vijayan:
http://xdaforums.com/showthread.php?t=2410844

no PC access to port..:(
[Captivate General] aliver.dun:
u will port it for captivate .thanks a lot ...
[Captivate General] ajeesh vijayan:
no PC right now
[Captivate General] mikhazloy:
i think this port is not necessary with such critical bugs:(
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Download & change-log

DOWNLOAD & CHANGE-LOG

** DISCLAIMER : FLASH AT YOUR OWN RISK **

WARNING :

* Under-volting can cause instability

* Over-clocking can cause freeze/reboot, heat & damage to CPU

* Any customizations may void warranty

P6810 Wi-Fi JB 4.1.2 DXMD3 ONLY

INSTALLATION

** DO NOT USE ANY 3RD PARTY TWEAKS OR “PERFORMANCE” TYPE APPS & REMOVE

ALL

ROM / KERNEL SCRIPTS FROM /system/etc/init.d FOLDER **

1. NANDROID (just in case)

2. Flash SkyHigh P6810 JB 4.1.2 ROM or bodivas P6810 JB 4.1.2 ROM

3. Remove any previous CPU control settings from starting at boot, remove any 3rd party tweaks etc

4. Flash in custom recovery (CWM or TWRP) to auto wipe previous kernel profile remnants ie. crontab & /data/.siyah folder

5. If requested by Recovery to install SU, DO NOT. Instead - Let the kernel do it on boot

P6810 Wi-Fi SkyHigh Kernel : Latest release is v3.0.0 FINAL Edition

CWM.zip v3.0.0 FINAL http://d-h.st/oVe

Archive : Working CWM Official Released Legacy Versions (UNSUPPORTED)

v2.6.0b

v2.5.0b

v2.4.0b

v2.3.0

v2.1.0

v2.0.0

v1.9.0

v1.8.0

v1.7.0

v1.6.0

v1.5.0

v1.0.0

-------------------------------------------------------------------

Stock repack kernel (thanks bodivas) :

CWM.zip DXMD3

ODIN.tar DXMD3

++ PLEASE DO NOT REDISTRIBUTE - LINK HERE INSTEAD ++ :)

BUGS

* Check if it is actually a stock firmware bug first using stock kernel -BEFORE- posting in this thread or elsewhere :cool:

1. Random screen tint reported on

both

stock & SkyHigh kernels using CPU control app (Read Post #3)

.

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
A few things to do yet to bring it on par with the P6800 SkyHigh kernel.

ie. exFAT, init.d (think not working), custom bootanimation & sound support, some more tweaks etc

Edit: forgot to mention, frandom is only 1/2 way there. Removed from initramfs SkyHigh install script as well. Will look into it in good time.

Please be patient, I have other things to do ;)
[Galaxy Tab 7.7 Android Development] karlsbug:
Thanks so much! Will flash asap.
[Galaxy Tab 7.7 Android Development] el_campi:
Downloading, thanks to make our tablet live.
[Galaxy Tab 7.7 Android Development] Beerkan:
Many thanks UpInTheAir..

You're the only reason my P6810 is not for sale.:highfive:
[Galaxy Tab 7.7 Android Development] Morloc2:
Thank you very much :D
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Just for a change, been having a play around cooking a test ROM and mods. Been a while since I've done that, but it's like riding a bike, little shaky a first, but never forget. ;) I have no plans for the ROM.

Will take a look at this kernel again tomorrow. Expect an update in the next day or so. :)
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Update on development.

Update on development.

Looks like the next update could be a little longer than hoped.

Have managed to get just about everything working same as current P6800 kernel (plus implementing fstrim lagfix on boot),.......

EXCEPT USB-OTG keeps constantly mounting/unmounting. Have not found the exact cause yet, and is something to do with the initramfs SkyHigh.sh install script or maybe the init.rc entry to initiate it.

I have compiled 20-30 kernels today, time for a break.......
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v1.5.0 update

>> v1.5.0 UPDATE <<

** FOR P6810 Wi-Fi device running bodivas JB 4.1.2 DXMD3 ROM Port ONLY !! **

++ SOMEONE PLEASE CONFIRM USB-OTG WORKS - I THINK MY ADAPTER IS BROKEN ++

1. Read warnings in Post #3 before flashing. I am not responsible, you are

2. Clear your CPU Control app defaults first. device settings/applications/all/"your control app"/clear data

3. You will need a CPU control app to adjust the CPU freq from the safe startup values (OC / UV / UC)

4. Recommend 200-1400 -or- 200-1600 MHz

5. Recommended governors etc = Read Post #3

CHANGE-LOG v1.0.0 -> v1.5.0

* R/W and auto-mounting of exFAT USB-OTG & external sdcard

* Modded ROM /system/etc/vold.fstab to permit exFAT mounting

* IO scheduler set the same for internal & external sdcards via initramfs : default = SIO

* Updated to SuperSU 1.65 & binary v1.61 (installs only if you don't have any)

* fstrim lagfix on boot (trims system, data & cache) - slows down reboot, but who cares, aren't we more concerned with using device?

* Frandom now working

* Fixed all initramfs mods & tweaks

* init.d support & set to 777

* Thunderbolt IO scheduler tweaks

* Power saving & virtual memory tweaks

* Increased windowsmgr.max_events_per_sec from 90 to 200

* External sdcard read ahead cache set to 1664 KB

* Custom boot animation support

* Custom boot sound support

* Removed some module debugging

* Force close freeze fix​

TO-DO

* Lots

INSTALLATION

1. NANDROID (just in case)

2. Flash bodivas P6810 JB 4.1.2 ROM Port

3. Remove any previous CPU control settings from starting at boot

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

4. THIS WILL PROBABLY "BREAK" currently installed V6SuperCharger scripts ! (test kernel first, and then re-install scripts)

5. Reboot again to fstrim your partitions

SUGGESTED CPU CONTROL APP : Trickster Mod app

Don't forget to use only one Control app at a time. They will conflict !

CURRENT BUGS :

* Random screen tint (Read Post #3)

* The CPU freq

may

exceed the max cap setting on wakeup. ie max CPU freq set @ 1400 MHz -> turn on screen -> 1600 Mhz very very briefly -> then back down

Can't fix the CPU Level 0 bug. Refer to my post HERE. It is a FIRMWARE bug present in both stock and SkyHigh kernels​

ISSUES?

* READ POST #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v1.6.0 update

>> v1.6.0 UPDATE <<

** FOR P6810 Wi-Fi device running bodivas JB 4.1.2 DXMD3 ROM Port ONLY !! **

1. Read warnings in Post #3 before flashing. I am not responsible, you are

2. Clear your CPU Control app defaults first. device settings/applications/all/"your control app"/clear data

3. You will need a CPU control app to adjust the CPU freq from the safe startup values (OC / UV / UC)

4. Recommend 200-1400 -or- 200-1600 MHz

5. Recommended governors etc = Read Post #3

CHANGE-LOG v1.5.0 -> v1.6.0

* Fixed my omission to make kernel insecure :eek:

* Disable modem in config file (our device is a WiFi model)

TO-DO

* Lots

INSTALLATION

1. NANDROID (just in case)

2. Flash bodivas P6810 JB 4.1.2 ROM Port

3. Remove any previous CPU control settings from starting at boot

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

4. THIS WILL PROBABLY "BREAK" currently installed V6SuperCharger scripts ! (test kernel first, and then re-install scripts)

5. Reboot again to fstrim your partitions

SUGGESTED CPU CONTROL APP : Trickster Mod app

Don't forget to use only one Control app at a time. They will conflict !

CURRENT BUGS :

* Random screen tint (Read Post #3)

* The CPU freq

may

exceed the max cap setting on wakeup. ie max CPU freq set @ 1400 MHz -> turn on screen -> 1600 Mhz very very briefly -> then back down

Can't fix the CPU Level 0 bug. Refer to my post HERE. It is a FIRMWARE bug present in both stock and SkyHigh kernels​

ISSUES?

* READ POST #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] el_campi:
No problems with usb-otg in 1.6.

Thanks UpInTheAir.

---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------

No problems with usb-otg in 1.6.

Thanks UpInTheAir.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
Thanks for confirming.

I wasted a lot of time "chasing my tail", so frustrating, but a relief it's was my adapter.

Looks like I need to eBay :)
[Galaxy Tab 7.7 Android Development] guisof:
Guys, you are marvelous !

From the Galaxy
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v1.7.0 update

>> v1.7.0 UPDATE <<

** FOR P6810 Wi-Fi device running JB 4.1.2 DXMD3 ROM !! **

1. Read warnings in Post #3 before flashing. I am not responsible, you are

2. Clear your CPU Control app defaults first. device settings/applications/all/"your control app"/clear data

3. You will need a CPU control app to adjust the CPU freq from the safe startup values (OC / UV / UC)

4. Recommend 200-1400 -or- 200-1600 MHz

5. Recommended governors etc = Read Post #3

** DELETE ANY INIT.D 90lagfix SCRIPT BEFORE FLASH **

CHANGE-LOG v1.6.0 -> v1.7.0

* Reverted in-built entropy generator for now

* Added sleep 60 command to lagfix script. Minimal impact on boot time now

* fstrim lagfix will now trim preload partition (there is

no app

that can do this, only this tweak !!)

* lagfix tweak can now be disabled and re-enabled. Please refer to Post #3

INSTALLATION

1. NANDROID (just in case)

2. Flash SkyHigh P6810 JB 4.1.2 ROM or bodivas P6810 JB 4.1.2 ROM

3. Remove any previous CPU control settings from starting at boot

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

4. THIS WILL PROBABLY "BREAK" currently installed V6SuperCharger scripts ! (test kernel first, and then re-install scripts)

5. Reboot again to fstrim your partitions

SUGGESTED CPU CONTROL APP : Trickster Mod app

Don't forget to use only one Control app at a time. They will conflict !

CURRENT BUGS :

* Random screen tint (Read Post #3)

* The CPU freq

may

exceed the max cap setting on wakeup. ie max CPU freq set @ 1400 MHz -> turn on screen -> 1600 Mhz very very briefly -> then back down

Can't fix the CPU Level 0 bug. Refer to my post HERE. It is a FIRMWARE bug present in both stock and SkyHigh kernels​

ISSUES?

* READ POST #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
V1.9.0 update

>> v1.9.0 UPDATE <<

** FOR P6810 Wi-Fi device running JB 4.1.2 DXMD3 ROM !! **

1. Read warnings in Post #3 before flashing. I am not responsible, you are

2. Clear your CPU Control app defaults first. device settings/applications/all/"your control app"/clear data

3. You will need a CPU control app to adjust the CPU freq from the safe startup values (OC / UV / UC)

4. Recommend 200-1400 -or- 200-1600 MHz

5. Recommended governors etc = Read Post #3

** REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

CHANGE-LOG v1.8.0 -> v1.9.0

** Source changes as per gitHub

* 4-step GPU Control interface (sysfs) via init.d script (EXAMPLES IN POST #3)

clock

voltage

step thresholds

stay counts​

* Change to lzo compression (slightly faster boot at expense of zImage size)

* xz compressor tweaked (not currently in use)

* SLUB - small performance tweak

* Stop compiling unuded 4x12 objects on 4210

* Corrected OP

INSTALLATION

** REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

1. NANDROID (just in case)

2. Flash SkyHigh P6810 JB 4.1.2 ROM or bodivas P6810 JB 4.1.2 ROM

3. Remove any previous CPU control settings from starting at boot

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

4. THIS WILL PROBABLY "BREAK" currently installed V6SuperCharger scripts ! (test kernel first, and then re-install scripts)

SUGGESTED CPU CONTROL APP : Trickster Mod app

Don't forget to use only one Control app at a time. They will conflict !

CURRENT BUGS :

* Random screen tint (Read Post #3)

ISSUES?

* READ POST #1, #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] UpInTheAir:
v2.0.0 update

>> v2.0.0 UPDATE <<

** FOR P6810 Wi-Fi device running JB 4.1.2 DXMD3 ROM !! **

1. Read warnings in Post #3 before flashing. I am not responsible, you are

2. Clear your CPU Control app defaults first. device settings/applications/all/"your control app"/clear data

3. You will need a CPU control app to adjust the CPU freq from the safe startup values (OC / UV / UC)

4. Recommend 200-1400 -or- 200-1600 MHz

5. Recommended governors etc = Read Post #3

** REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

CHANGE-LOG v1.9.0 > v2.0.0

** Source changes as per gitHub

* Increased from 4 to 5-step GPU : Default = 108-160-267-330-400 MHz

Min freq = 54 MHz (lower than 108 MHz may cause lag, freeze or SOD)

Max freq = 520 MHz

Valid freq (useable) = 54-66-108-160-160-200-267-300-330-400-440-520 MHz

Voltage = 800 > 1200 mV (+/- 50 mV increments)

Stock = 2-step GPU (160-267 MHz)​

* GPU UV / UC / OC

108 MHz = 900mV

160 MHz = 900mV (-100 mV > stock 1000 mV)

267 MHz = 950 mv (-150 mV > stock 1100 mV)

330 MHz = 1000 mV

400 MHz = 1050 mV​

* 5-step GPU Control interface (sysfs) via init.d script Control interface (EXAMPLES IN POST #3)

clock

voltage

step thresholds

stay counts​

* Fixed GPU staycount interface not applying changes

* Lower GPU idle (screen off) freq to 108 MHz & voltage to 900 mV

* Lower min GPU configurable voltage to 800 mV

Default still = 900 mV for stabilty (lower may cause freeze or SOD - depends on device)

Stable 108 MHz @ 800 mV

on my device

, maybe not yours?​

* Tweak GPU freq thresholds

INSTALLATION

** REMOVE

ALL

PREVIOUS SkyHigh ROM SCRIPTS FROM /system/etc/init.d FOLDER (EXCEPT: sqlite & ziplaign are OK) **

1. NANDROID (just in case)

2. Flash SkyHigh P6810 JB 4.1.2 ROM or bodivas P6810 JB 4.1.2 ROM

3. Remove any previous CPU control settings from starting at boot

4. Flash in :

a) CWM.zip in custom recovery (CWM or TWRP)

-or-

b) ODIN.tar in Odin [PDA] / Mobile Odin
​

4. THIS WILL PROBABLY "BREAK" currently installed V6SuperCharger scripts ! (test kernel first, and then re-install scripts)

SUGGESTED CPU CONTROL APP : Trickster Mod app

Don't forget to use only one Control app at a time. They will conflict !

CURRENT BUGS :

* Random screen tint (Read Post #3)

ISSUES?

* READ POST #1, #2 & #3 FIRST

CHEERS :D

UITA

.
[Galaxy Tab 7.7 Android Development] karlsbug:
Anybody else having problems with the download links for the latest update?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
Hi Guys,

My sm-n9005 often disconnects from my wifi (fritzbox) and shows "you are not logged in" in the notification centre...

Only appears wirh Fritz!Box all other routers are okay.

I am on mi7 unbranded (former german tmobile device)

Do you think an update to mj3 will fix this?