[ROM] [JB] [4.1.2] Stock deodexed and rooted XXLSA / NEW Leak!

[ukjeeper]

seems there are wake locks. remove the battery for a while and reinsert and test again. also make sure GPS is off when not in use

I'll give it a try. Thanks.

 

[cimbike]

Has anyone tried latest PhilZ kernel?

 

[FireWall123]

Has anyone tried latest PhilZ kernel?

Yes any questions ?

Sent from my GT-N7000 using Tapatalk 2

 

[evanbigfan]

Where can i find the older version of viber?

try aptoide.apk it has many apk for free

Sent from my GT-N7000 using xda premium

 

[jjamain]

Has anyone tried latest PhilZ kernel?

Yes. No problem.

sent by flasholic from tapatalk 2

 

[cimbike]

Thanks. I have already flashed latest PhilZ kernel and also modded with lock screen ink efect and works fine and battery life is great.

 

[sabbathmaniac]

Came from JellyBeen_eybee1970.zip to this. Battery life is...disappointing. Lost 40% last night while i slept (7 hours). A lot worse off than i was with eybee1970.

Same apps. Should be way better, especially as Note now is used a lot less since i got my Tab 2 10.1 for media useage.

CPU spy showing plenty of deep sleep, 47%.
200Mhz, 34%.
Every other Mhz, below 9%.

Battery meter showing:
Android OS 26%
Device Idle 19%
Cell Standby 16%
Screen 11%
Maps 7%
Mediaserver 6%

Did you try to do ?

1. Turn of WiFi and Bluetooth
2. Haptick feedbck is off from sittings - sound
3. Enable power saving with all its sub options
4. Turn off GPS
5. Wake up Command in Voice Talk is OFF
6. Reboot in recovery and reset battery stats then reboot back into android OS, recharge again and keep an eye on it.

Hope this can help with your battery issue

 

[leonidas540bc]

Ok guys I've been trying to identify any apps that may cause the boot loop. I had it happen on numerous roms including stock! I've narrowed it down to CPU spy. It's the only app I've not installed in my last five roms and since then I've not had a boot loop issue. Any thoughts on this?

Sent from my GT-N7000 using xda app-developers app

 

[REVERSiN]

Ok guys I've been trying to identify any apps that may cause the boot loop. I had it happen on numerous roms including stock! I've narrowed it down to CPU spy. It's the only app I've not installed in my last five roms and since then I've not had a boot loop issue. Any thoughts on this?

Sent from my GT-N7000 using xda app-developers app

Unlikely, I don't use CPUSpy yet had several reboots, issue is caused by something else, not preload nor 3rd party apps nothing related to this... Tried everything nothing helps I even used aroma file manager to checkup on files if any is deleted or destroyed but none :/

Sent from my GT-N7000 using Tapatalk 2

 

[rraaka]

im a regular user of cpu spy.
The problem i had was not bootloops but getting stuck on samsung logo after flashing a cwm zip file. the only way out in this situation was to factory data reset. for which i preferred manual inclusion of files. to flash phillz newer versions of kernel i prefer the tar file through mobile odin.

with Burts lsc i havent had these problems to that extent.....lesser. mods from olefiax, xperiacle have been smooth experiences for me.

Phil suggested that the fault may lie with the deodexing of the rom ...i m not sure about that.

every day we think we are closer to an official JB, so why waste time trying to deodex again ? lsa with its MTP problem isnt worth the trouble.

 

[REVERSiN]

im a regular user of cpu spy.
The problem i had was not bootloops but getting stuck on samsung logo after flashing a cwm zip file. the only way out in this situation was to factory data reset. for which i preferred manual inclusion of files. to flash phillz newer versions of kernel i prefer the tar file through mobile odin.

with Burts lsc i havent had these problems to that extent.....lesser. mods from olefiax, xperiacle have been smooth experiences for me.

Phil suggested that the fault may lie with the deodexing of the rom ...i m not sure about that.

every day we think we are closer to an official JB, so why waste time trying to deodex again ? lsa with its MTP problem isnt worth the trouble.

I can deodex it again but not sure its the problem, a FedEx fault error will cause many boot loops (on first run not of a sudden), and the issue is it might have force closes, thing which don't work... Unlike these symptoms......

I haven't experienced any normal boot loops so to say, only getting stuck on GT logo and yes a factory reset only helps weired but I dunno what to say, some guys reported this on STOCK ROMs...

I am back to LSA, getting my ROM ready and will continue testing it, many say LSA it the most stable on these leaks... So we do and try!

Sent from my GT-N7000 using Tapatalk 2

 

[judhi]

Flashing with Mobile Odin

First of all, thanks to everyone who spent their great effort to make this happen.

I used CWM to reset to factory default, boot to recovery, format and install the ZIP.
Unfortunately it stuck at around 20%, the progress bar was just not moving anymore.
So I removed the battery and let it boot normally to stock ICS (well, this unit originally came with GB and I flashed it ICS XXLRK last year).
I reinstall Mobile Odin Pro from my backup folder and use it to install the XXLSA.

Installation went smoothly and successful!

Everything goes well except that I noticed the battery drained faster than before when I use the device for browsing.
Not sure why, but now I use Antutu CPU Master to speed limit the CPU to only 1000 MHz instead of full 1400, let see if there's any improvement.

Cheers!
Judhi

 

[rraaka]

I can deodex it again but not sure its the problem, a FedEx fault error will cause many boot loops (on first run not of a sudden), and the issue is it might have force closes, thing which don't work... Unlike these symptoms......

I haven't experienced any normal boot loops so to say, only getting stuck on GT logo and yes a factory reset only helps weired but I dunno what to say, some guys reported this on STOCK ROMs...

I am back to LSA, getting my ROM ready and will continue testing it, many say LSA it the most stable on these leaks... So we do and try!

Sent from my GT-N7000 using Tapatalk 2

Reversin, for sake of discussion, if you read into the poll on Phills kernel thread (read well into it) i think members of community actually voted for this bugginess !! :cyclops:

 

[shoey63]

AFAIK, All LSA/LSC leaks, whether odexed or deodexed, regardless of running stock, Philz or Alliance kernel will randomly get stuck on Samsung splash screen on reboot. Also lags after a few days and sometimes irrecoverable
loss of root.Many think the culprit is Philz kernel because occasionally it happens on the reboot after flashing. However getting stuck/bootloop can happen after any power cycle.

Edit: I'm on LS4 and none of the above issues have occurred.
Sent from my GT-N7000 using xda app-developers app

 

[REVERSiN]

AFAIK, All LSA/LSC leaks, whether odexed or deodexed, regardless of running stock, Philz or Alliance kernel will randomly get stuck on Samsung splash screen on reboot. Also lags after a few days and sometimes irrecoverable
loss of root.Many think the culprit is Philz kernel because occasionally it happens on the reboot after flashing. However getting stuck/bootloop can happen after any power cycle.

Edit: I'm on LS4 and none of the above issues have occurred.
Sent from my GT-N7000 using xda app-developers app

Was too laggy for me, its slow compared to others...

Reversin, for sake of discussion, if you read into the poll on Phills kernel thread (read well into it) i think members of community actually voted for this bugginess !! :cyclops:

Sorry mate, I use tapa talk and it shows no polls

Sent from my GT-N7000 using Tapatalk 2

 

[cimbike]

To get rid of stuck Samsung logo on reboot it's been said to get all the way back to Honeycomb then to ICS stock rom and.finally flash Jelly Bean again.

 

[FireWall123]

To get rid of stuck Samsung logo on reboot it's been said to get all the way back to Honeycomb then to ICS stock rom and.finally flash Jelly Bean again.

Not honeycomb lol , its gingerbread

Sent from my GT-N7000 using Tapatalk 2

 

[cimbike]

yea, you are right. Gingerbread, sorry.

 

[jasonhoch]

AFAIK, All LSA/LSC leaks, whether odexed or deodexed, regardless of running stock, Philz or Alliance kernel will randomly get stuck on Samsung splash screen on reboot. Also lags after a few days and sometimes irrecoverable
loss of root.Many think the culprit is Philz kernel because occasionally it happens on the reboot after flashing. However getting stuck/bootloop can happen after any power cycle.

Edit: I'm on LS4 and none of the above issues have occurred.
Sent from my GT-N7000 using xda app-developers app

I am agree with u. my note has noticeable lag before it restarted itself and stucked. tried both lsa and lsc, but all are same issue.

Sent from my GT-N7000 using xda app-developers app

 

[rraaka]

AFAIK, All LSA/LSC leaks, whether odexed or deodexed, regardless of running stock, Philz or Alliance kernel will randomly get stuck on Samsung splash screen on reboot. Also lags after a few days and sometimes irrecoverable
loss of root.Many think the culprit is Philz kernel because occasionally it happens on the reboot after flashing. However getting stuck/bootloop can happen after any power cycle.

Edit: I'm on LS4 and none of the above issues have occurred.
Sent from my GT-N7000 using xda app-developers app

ive been pretty stable lately with lsa, lsc and ls7 and want to thank again the devs who made these leaks available

i dont mind if my Note stays on lsc for the rest of her life with me

ls4 was a controversial entry and it just doesnt have enough mods fine tuned for it.

but the bugs cant be overlooked ......lest they recur with official JB when and if it comes .....

and I can be a strong critic of the things i love :silly: