Database Info

[Q] help! how to flash franco kenerl in Liquidsmooth rom ( nexus 5)

Brothers! any one can help me to solve the problem?
I am using nexus 5 and just flash liquidsmooth rom. I always use Franco kenerl, however, after I flash Franco kenerl in this rom, I cannot enter to the system again and keep on the opening screen. Anyone know what is the matter? can solove it? Thanks!

nickho0911 said:
Brothers! any one can help me to solve the problem?
I am using nexus 5 and just flash liquidsmooth rom. I always use Franco kenerl, however, after I flash Franco kenerl in this rom, I cannot enter to the system again and keep on the opening screen. Anyone know what is the matter? can solove it? Thanks!
Click to expand...
Click to collapse
Any one could help me??? Thanks.

nickho0911 said:
Any one could help me??? Thanks.
Click to expand...
Click to collapse
"Franco.Kernel doesn't support CM11. It's due to some stuff with CAF, idk. Confusing to me. . There's a fix on XDA in the Android Development Section.
You should give AOSPAL a try. Many features, very stable. "
i found that on another page, may be you have a look for the fix
Edit:
BTW
THE FIRST TEXT IN BIG RED LETTERS on the franco's kernel thread is:
"Currently does not work with recent CyanogenMod nightlies or any rom has uses CM sources as a base because they made underlying changes that are now incompatible with Kernels that don't follow their path."
May be have a look before installing anything and get some informations about what you're going to do. Or you will may be brick your device, just because reading is to stressfull to you...

LS.xD said:
"Franco.Kernel doesn't support CM11. It's due to some stuff with CAF, idk. Confusing to me. . There's a fix on XDA in the Android Development Section.
You should give AOSPAL a try. Many features, very stable. "
i found that on another page, may be you have a look for the fix
Edit:
BTW
THE FIRST TEXT IN BIG RED LETTERS on the franco's kernel thread is:
"Currently does not work with recent CyanogenMod nightlies or any rom has uses CM sources as a base because they made underlying changes that are now incompatible with Kernels that don't follow their path."
May be have a look before installing anything and get some informations about what you're going to do. Or you will may be brick your device, just because reading is to stressfull to you...
Click to expand...
Click to collapse
Thank you so much! Then, i am considering another custom rom because my main concern is the battery life and smoothness. Do you have any recommend custom rom to me? Thanks.

Not by self experience Cause I use HTC/Samsung at the moment
Gesendet von meinem One S mit Tapatalk

TWRP 2.7 for HTC Desire S

Hi. As you propably know, there is no TWRP 2.7 for saga. This is why:
Saga would need a number of updates in order to make it work with 4.4 Kit Kat ROMs. 4.4 ROM support really doesn't depend on the recovery itself. The kernel and other parts of the ramdisk have to support SELinux contexts in order for the set_metadata functions to work. I don't have a saga myself and at this point I have no plans to continue to support the device. I've been building saga in a CM7 / gingerbread tree which doesn't support the things needed for SELinux. The device would need to be compiled with an updated kernel in at least a 4.1 and preferably a 4.3 or 4.4 tree to support installing Kit Kat ROMs.
I plan to drop official support for any device that I've been building in ICS or Gingerbread trees which includes saga. If people want to see continued support for those devices, then hopefully developers for those devices will step up and build TWRP themselves and maybe offer their updated device files to us so that we can extend official support.
Click to expand...
Click to collapse
So basically we need developers who would like to help with that. I'm not that techy to understand what the problem is but I would like you to tell me and help.
BTW! Why our device is not available in DevDB! How do we change that?

Hm. I might take a shot at this. Though I personally prefer 4ext

devil-kin said:
Hm. I might take a shot at this. Though I personally prefer 4ext
Click to expand...
Click to collapse
It would be really splendid thing to do sir

Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.

devil-kin said:
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
Click to expand...
Click to collapse
That's great! It would be even better if you could somehow share some of your work here so maybe someone else could take a look (i don't know if it's possible. But you use github right?) I would love to add this project to DevDB but it seems that our phone is not there and i don't know how to add it.

My github repos are at https://github.com/jdeluyck - I haven't uploaded anything yet save for the changes to the repo file to pull in TWRP.

Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know

PERFECT!
devil-kin said:
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
Click to expand...
Click to collapse
I flashed it, I backed up my rom, I wiped, I flashed my rom clean, it booted, I went to recovery and I restored my rom. Everything went perfect, no problems whatsoever! Now there are 2 questions left to ask.
1. May I update TWRP for saga developement thread and attach this build?
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Anyway great work devil-kin :highfive: Personally I see TWRP as the best recovery and I'm on it from 2.2. Seeing it still working in its latest iteration on my beloved DS makes little tears appear in the corners of my eyes. I absolutely love this phone for it's size, specs, build quality and weird survability (many screen to sidewalk encounters and no broken glass Only praiseworthy scars). LONG LIVE DS! <3

VnnAmed said:
1. May I update TWRP for saga developement thread and attach this build?
Click to expand...
Click to collapse
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
VnnAmed said:
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Click to expand...
Click to collapse
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?

devil-kin said:
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
Click to expand...
Click to collapse
Thank you very much If you could, i would like you to PM Dees_Troy and tell him that you have succesfully compiled 2.7 for saga, so if he has some more technical questions you can answer them I'm updating TWRP for saga thread right away

[Q&A] [ROM][UNOFFICIAL][4.4.4][OCT-16] CyanogenMod 11 HTC One S [hboot 2.16]

Q&A for [ROM][UNOFFICIAL][4.4.4][OCT-16] CyanogenMod 11 HTC One S [hboot 2.16]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

where is 16/10 nightie?
cikoleko said:
#Added 16/10
#NOT Tested
Last commit:
Click to expand...
Click to collapse
I only see 17/10 night build and surprisingly links to 18/10, althrough these 18/10 links leands to 404 - page not found.
I'm asking because I believe something goes wrong with latest build.
my android.phone app keeps crashing all the time even after I reinstall M11 from scratch.
and maybe it's only a side effects of my todays experiments, but after fastboot flash boot boot.img I see that HBOOT still stays with version 2.15, instead of expected 2.16.
is it normal? or is it my own fault?

pavel.bosco said:
I only see 17/10 night build and surprisingly links to 18/10, althrough these 18/10 links leands to 404 - page not found.
I'm asking because I believe something goes wrong with latest build.
my android.phone app keeps crashing all the time even after I reinstall M11 from scratch.
and maybe it's only a side effects of my todays experiments, but after fastboot flash boot boot.img I see that HBOOT still stays with version 2.15, instead of expected 2.16.
is it normal? or is it my own fault?
Click to expand...
Click to collapse
Check both links and double check the latest files:
https://drive.google.com/?usp=chrome_app#folders/0B_THDHRTYTJTQlBlb0lqYXJjTWs
http://forum.xda-developers.com/devdb/project/?id=2604#downloads
The ROM in this thread is made for HBOOT 2.16 users, if you have HBOOT 2.15, this ROM isn't compatible with your firmware. There's official CM11 thread for HBOOT 2.15
Basically if you're on HBOOT 2.15 you use OFFICIAL builds, if you're on HBOOT 2.16 you use UNOFFICIAL BUILDS.
I only see 17/10 night build and surprisingly links to 18/10, althrough these 18/10 links leands to 404 - page not found.
Click to expand...
Click to collapse
From what I understand you are referring to CMXLOG, if you have HBOOT 2.16, this is only to show what changes have been made to the ROM as they are identical to what is included in the OFFICIAL CM11 ville builds but you can't download and flash it on HBOOT 2.16. Again it's just to check what has been added to the build.
So because my builds are UNOFFICIAL, I build when I can. For example if the OFFICIAL NIGHTLY was released on 17/10 but the latest commit of that NIGHTLY was merged on 16/10 and straight away I built that, that's why the date differs.

cikoleko said:
Check both links and double check the latest files:
https://drive.google.com/?usp=chrome_app#folders/0B_THDHRTYTJTQlBlb0lqYXJjTWs
http://forum.xda-developers.com/devdb/project/?id=2604#downloads
The ROM in this thread is made for HBOOT 2.16 users, if you have HBOOT 2.15, this ROM isn't compatible with your firmware. There's official CM11 thread for HBOOT 2.15
Basically if you're on HBOOT 2.15 you use OFFICIAL builds, if you're on HBOOT 2.16 you use UNOFFICIAL BUILDS.
From what I understand you are referring to CMXLOG, if you have HBOOT 2.16, this is only to show what changes have been made to the ROM as they are identical to what is included in the OFFICIAL CM11 ville builds but you can't download and flash it on HBOOT 2.16. Again it's just to check what has been added to the build.
So because my builds are UNOFFICIAL, I build when I can. For example if the OFFICIAL NIGHTLY was released on 17/10 but the latest commit of that NIGHTLY was merged on 16/10 and straight away I built that, that's why the date differs.
Click to expand...
Click to collapse
thank you for such detailed answer. indeed I felt into huge hole full of interconnected misunderstandings. for some reason I decided that official only supports 2.16 and also makes lot of such wrong assumptions.
I don't know that happens with my official CM11, but really android.phone app on it started to crash again and again after some update. nothing helps.
hopefully my journey finished successfully. I'm now S-OFF, rooted, superCIDed and on HBOOT 2.16 with almost latest nightly _unofficial_ CM11 build. two days lost on that way.
sorry if my post makes any confusion and thank you for your patience and every day job on handling this builds.

Just tested SNAPSHOT-M11/PA-GApps (stock package) clean install after factory reset, everything is working fine.

cikoleko said:
Just tested SNAPSHOT-M11/PA-GApps (stock package) clean install after factory reset, everything is working fine.
Click to expand...
Click to collapse
so I'm on 11-20141016UNOFFICIAL-ville. Phone works, no problem, thanks
if I press "system update" I see cm-11-201410[17, 18, 19]-NIGHTLY (3 updates), are they all compatible, i.e. unofficial? or this is not how it's supposed to work with unofficial ROM? is the update procedure for UNOFFICIAL differ from OFFICIAL one?

pavel.bosco said:
so I'm on 11-20141016UNOFFICIAL-ville. Phone works, no problem, thanks
if I press "system update" I see cm-11-201410[17, 18, 19]-NIGHTLY (3 updates), are they all compatible, i.e. unofficial? or this is not how it's supposed to work with unofficial ROM? is the update procedure for UNOFFICIAL differ from OFFICIAL one?
Click to expand...
Click to collapse
I actually already explained it in the thread, if you read below 'installation instructions' you'll see it:
NOTE: Don't install updates offered by OS as they are official updates and are not compatible with hboot 2.16
Click to expand...
Click to collapse

cikoleko said:
I actually already explained it in the thread, if you read below 'installation instructions' you'll see it:
Click to expand...
Click to collapse
got it, thanks. I was mistakenly thinking that you talk about market apps updates and I was trying to escape them.

Wow, having FM supported sound very promising.
Is it my only experience of sound during the call is really low?
Both loud speaker and phone are difficult to listen during the call.
But navigator application which I use, speaks very loud, just as it did on stock FW.
is a problem with application? How can I tune it to work better?

the FM app you mentioned works fine with 16-10-2014 nighty build
thanks for pointing out. I only doubt why it request so lot of capabilities, like root (?), blue tooth, calls and so on
but it seems to work, which is avesome.

cikoleko said:
After I done it my phone is stuck on boot animation
Click to expand...
Click to collapse
as I understand, default editor for some reason fails during save of that file, I edited it using laptop and put it back in recovery, setting 755 permission. After that phone boot up successfully.
You can "repair" stucked phone next time with original file from ROM image.
mikronac.ns said:
Hey HBoot 2.16 lovers. Have you random reboots sometimes?
Click to expand...
Click to collapse
yes, I see about 3 times per week, and not sure how much times I just don't see it, since I don't set up any PIN lock
not sure what is the reason and that are the circumstances

cikoleko said:
#Added 02/11
#NOT tested
Click to expand...
Click to collapse
please have a look at next nighty, seems like this bug-fix http://review.cyanogenmod.org/#/c/76150/ could make voice during the call sounds better, isn't it?

cikoleko said:
#Added 08/11
#NOT tested
Click to expand...
Click to collapse
I couldn't comment on main thread. Just wanna say I flash this ROM and this time sound is much louder, it is such good as it should be.
so if you or someone else have same problem with volume as I did, try this ROM, hopefully it is better.
I've not tried anything else so far, at least it started and could answer and make a call

[ROM][UNOFFICIAL][4.4.4][OCT-16] CyanogenMod 11 HTC One S [hboot 2.16]
Hi,
I installed CM11 a week ago and I noticed that the phone does not vibrate! Today I did the update to the latest version and still doesn't work .. I have searched on the internet but cant find a solution.
Any tips?
Thanks

[Q&A] ★☆★[ROM] [ALPHA] One+ VM12 v1.0.0|LRX22G & VM12.1 [LMY47D] |

[Q&A] ★☆★[ROM] [ALPHA] One+ VM12 v1.0.0|LRX22G & VM12.1 [LMY47D] |
Q&A for ★☆★[ROM] [ALPHA] One+ VM12 v1.0.0|LRX22G & VM12.1 [LMY47D] |★☆★
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for ★☆★[ROM] [ALPHA] One+ VM12 v1.0.0|LRX22G & VM12.1 [LMY47D] |★☆★. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

störte said:
On my phone density dies not change. Tried build in and also external APP. Even changing buildprop manually dont work.
It was dirty flash
Send by Hyperdrive on one+One
Click to expand...
Click to collapse
vinman12 said:
Worked here, do u have super su installed and up to date binarys
Click to expand...
Click to collapse
Density doesn't work for me too, clean flash and I have Super Su

Novacane7 said:
Density doesn't work for me too, clean flash and I have Super Su
Click to expand...
Click to collapse
We just implemented that today and are working hard to get it and our other list of mods ported over.

titanium backup / OT
netcitizen said:
tibu won't work without root . or is there any specific setting in tibu for gapps ? they are tiny but while flashing ROMs frequently it is a pain to install from play store.
Click to expand...
Click to collapse
Are you flashing tibu in recovery? Launch Tibu, go to menu and create 'update.zip' and be sure to create it as a system application. Reboot and flash the zip. You need a pro key

damage98 said:
Are you flashing tibu in recovery? Launch Tibu, go to menu and create 'update.zip' and be sure to create it as a system application. Reboot and flash the zip. You need a pro key
Click to expand...
Click to collapse
I flash tibu like this only. I was talking about restoring gmail, hangouts , google calendar,maps using tibu since these apps are not in the 5.1 gapps package.

Thanks
This is a solid build very satisfied with the way that you have done this......
Thanks to all the developers.....

Great ROM working perfectly . thanks and congratulations
---------- Post added at 07:24 PM ---------- Previous post was at 07:17 PM ----------
Can we expect a new build for today
??

Totally fantastic rom! Going to try it out and report. Thank you so very much!
Sent from my A0001 using XDA Premium HD app

Asserts error during the flashing your rom, any suggestions how can I flash without this errors?

dirty flash over previous and playstore app can't connect to server.

Same issue with camera-mod here here. But not even a reboot helped. Can't start the camera app anymore.
I started stock-camera and switched between front and back - no problems. But the camera-mod keeps telling me that it was stopped, every time I try to start it.

camera-mod bug in vm12.1
now I re-flashed the camera-mod and it still doesn't work
so I got back to Open Camera and I love it

quick boot
When i enabled quick boot mode in developer settings.. BOOM!!! The os crashed.. followed by bootloop.. Then i again.. Clean installed the rom. Other than that no problem. Its a very stable rom and that too for a rom in alpha stage.. Its unbelievable.. !! Good work guys!!

kalali said:
dirty flash over previous and playstore app can't connect to server.
Click to expand...
Click to collapse
You should flash the gapps again.

Im willing to try out this ROM and experience 5.1 improvements. What are things that I should look out for before flashing? Are calling, texts, camera. etc working. Is it stable *enough*

Hey i got one question
I tried flashing the rom for severak hours, but I always get this error.
E:Cannot execute binary file.
I tried dirty flash, full wipe, even flashing from a clean install of CM11.
Can anybody help me?

download link dead
hey, just wanna say your link for OPO team nocturnal rom is dead

Awesome Work!
Hats off to Team Nocturnal for an an amazing piece of work. Can't thank you enough
Everything seems to be working flawlessly on built VM12.1 - 20150410 (radio, BT, GPS, sensors, etc) and I'm already into one week of flashing this rom. No lags or FCs whatsoever. I must admit, since first introduced to custom rom flashing, I've become
somewhat a flash junkie. Sometimes, switching roms on daily basis but this rom has given me no excuse.
Just one question though. Is, 6xxmb ram usage (with only basic system apps running) considered as memory leak?
I understand it's a common issue when running Lollipop.
Thanks again guys. Looking forward to future updates. (This is already perfect but I can't help it -Never Settle!)

Missing Appops
Hi. Thanks for the ROM. Are loving it, and at very impressed. I am missing Appops though. Hand I not done something? I flashed clean, then Gaps, then SU. Using the 15th April build.

Modem
Hi,
I had an issue of not receiving texts/sms/phone calls ON wifi.
I had this issue with Temasek's build and then switched to Nocturnals and the ROM still had this issue. I ended up going over to Blisspop's thread and using a modem alpha build they listed and this fixed the issue. Just FYI because I never had a funky issue with modem's or not receiving text/phone calls on wifi. Everyone else worked fine while off of wifi.
Other than that, I've played around with the ROM and it truly is a great experience with smoothness, now I'll be checking out that battery life!
Thanks team.

[Q&A] [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake

Q&A for [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][ALPHA][LP 5.1]CyanogenMod 12.1 Kernel with DoubleTap2Wake. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Bootloop after flashing. Help!
Need some help. I have installed this kernel on CM 12.1 Rohan's build and got bootloop... Some info: I used Philz Touch 6 Fota and wiped cache and dalvic after flash. I recovered from soft brick through but what should I do to avoid bootloop?

File
Sorry for the dumb question but what is zip dl-0? cant flash it, it wont detect it.

Good day. First off, i wanted to say that i've tried this kernel and the d2w is very helpful for preserving the hw power button and i think this kernel is very useful.
The thing is, since their latest releases, i've found that Glade Rom and SlimLP have been the roms that are best for me in terms of what i need and my daily usage. Unfortunately, this kernel doesn't work for either of them. I'm guessing it's because of their base?
Anyway, i'd like to ask if the dev has any plans to get this kernel working for either of those roms or for aosp 5.1.1 roms in general? If yes, that would be awesome. If not, then i still say this kernel's features are still very helpful and i'll be waiting to get a cm-based rom that works for my needs. ?

cascabel said:
Good day. First off, i wanted to say that i've tried this kernel and the d2w is very helpful for preserving the hw power button and i think this kernel is very useful.
The thing is, since their latest releases, i've found that Glade Rom and SlimLP have been the roms that are best for me in terms of what i need and my daily usage. Unfortunately, this kernel doesn't work for either of them. I'm guessing it's because of their base?
Anyway, i'd like to ask if the dev has any plans to get this kernel working for either of those roms or for aosp 5.1.1 roms in general? If yes, that would be awesome. If not, then i still say this kernel's features are still very helpful and i'll be waiting to get a cm-based rom that works for my needs. ?
Click to expand...
Click to collapse
Doesn't work in the sense?
I have plans to bring this to every LP based ROM for XL.
I guess there might be some kernel related change. I will see to it.

corphish said:
Doesn't work in the sense?
I have plans to bring this to every LP based ROM for XL.
I guess there might be some kernel related change. I will see to it.
Click to expand...
Click to collapse
bootloops. even through a clean install or flashing it after an install and clearing dalvik and cache...
i've noticed that the roms that doesn't work with tz 4.15 won't work with this kernel either.
great to hear your plans. really appreciate it.
edit:
both these roms are aosp based and have RRO supported as opposed to cm theme engine. could that have any bearing on it? let me know how i can help.

Problem on my HTC One (M7)
Hello,
first of all I would like to apologize for my English problems. I installed your Kernel on my HTC ONE M7. It is running on Cyanogenmod 12.1 (Android 5.1.1). The problem is that my handy freezes everytime it tries to boot. It freezes on the HTC logo to be more specific. Please let me know if you need to know more details or need even a log and I hope this issue gets solved.
Thank you

usb619 said:
Hello,
first of all I would like to apologize for my English problems. I installed your Kernel on my HTC ONE M7. It is running on Cyanogenmod 12.1 (Android 5.1.1). The problem is that my handy freezes everytime it tries to boot. It freezes on the HTC logo to be more specific. Please let me know if you need to know more details or need even a log and I hope this issue gets solved.
Thank you
Click to expand...
Click to collapse
LOL No, this kernel is not meant for HTC One.
This kernel is only for Sony Xperia L. Please read the full post before trying anything.
Now how to recover? If you are able to go in recovery, flash CM12 or any custom ROM.
Master Solution is flashing stock as always, although I dont know how things are done for HTC [emoji14]

@corphish i kniw i shouldn't but.. If it's possible, may i ask that you add the Intelliactive scheduler if you can? Lulzactive and on demand doesn't really work for me (lulzactive seemed buggy last time i tried it - main core stayed on max freq). Just a request. ?

Wifi stopped working after I flashed this kernel. Previously I was on Tz 4.16. Any ideas what I can do fix this, other than going back to Tz?

primemonitor said:
Wifi stopped working after I flashed this kernel. Previously I was on Tz 4.16. Any ideas what I can do fix this, other than going back to Tz?
Click to expand...
Click to collapse
Well, you cannot go back to TZ now. It flashes kernel in boot-device linked partition, which is a mystery partition about which only Varun knows.
I haven't succeeded in your situation.
Sent from my C2104 using Tapatalk

corphish said:
Well, you cannot go back to TZ now. It flashes kernel in boot-device linked partition, which is a mystery partition about which only Varun knows.
I haven't succeeded in your situation.
Sent from my C2104 using Tapatalk
Click to expand...
Click to collapse
Right, learned that the hard way
Is this a known issue though, or something that you or others have previously faced, that changing from Tz to Zapdos will break wifi? Just curious.

Hey man, I use Primexperia rom, it's CM12 based, soon to be posted new ver CM12.1 based. For some reasons it's not compatible with TZ 4.16, 4.14 only (wi fi missing on 4.16) Will this kernel work for me? The only thing I really need is a stable system with Sony sound
Oh almost forgot, I use TWRP and I think that any other recovery is a waste of time, to be honest. Can I use TWRP?

illague said:
Hey man, I use Primexperia rom, it's CM12 based, soon to be posted new ver CM12.1 based. For some reasons it's not compatible with TZ 4.16, 4.14 only (wi fi missing on 4.16) Will this kernel work for me? The only thing I really need is a stable system with Sony sound
Oh almost forgot, I use TWRP and I think that any other recovery is a waste of time, to be honest. Can I use TWRP?
Click to expand...
Click to collapse
I tried, breaks network .
Sent from my C2104 using Tapatalk

corphish said:
I tried, breaks network .
Sent from my C2104 using Tapatalk
Click to expand...
Click to collapse
Stryder modded the rom while he had TZ installed ... I dont get why but thats it... Flash TZ4.15 and then TZ4.16
Sent from my Xperia T using XDA Free mobile app

Stryflex LP 1.5 Rom
Hi,
I am using Stryflex LP 1.5 Rom.
When used the its kernel,phone freezes randomly & hangs & not responds.
We have to take out battery & restart phone.
Most of the times even if i take out from pocket also it is in DeadState(even if pressed power button alos nothing works.)
So i installed Thunderzap 4.16 ,it is not freezing but Wifi is not working.
Then i shifted to your kernel, thank god it is not at all freezing while operating .
But i noticed that it is going to black screen/Dead State very frequently.
Waiting for any suggestions & help.
I appreciate your help & time.

Could we get 1.7~ OC like in TZ kernel? It was fully stable for me even with thermal throttling disabled.

Maybe it's noob but would the wake up signatures Hurt the touchscreen some how.
I mean it well make it work for 24 hour????

Tz 4.16 with cm 12 work properly and Wi-Fi is goog and with application tenderzap control you can Cheng setting so good and you can change control charge to 2100 ma for faster charging so download tanderzap control.apk
Sent from my C2105 using Tapatalk
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
After installing rom should install tanderzap.zip with via recovery for resolve Wi-Fi problem
Sent from my C2105 using Tapatalk