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
Related
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
bboygmoney said:
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
Click to expand...
Click to collapse
ditto, this happend with my Paranoidandroid install as well. kernel allowed me to stay running without crash, but wifi is a pretty big letdown...
unfortunatly, without the kernel itself being fixed, or the wifi module fixed, we are stuck looking for another alternate kernel... oh yeah, we are pretty limited.
thanks
appreciate the quick reply man. And I'll be keeping my eye out then
bboygmoney said:
appreciate the quick reply man. And I'll be keeping my eye out then
Click to expand...
Click to collapse
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
bboygmoney said:
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
Click to expand...
Click to collapse
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
dakunesu said:
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
Click to expand...
Click to collapse
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
problem solved!
bboygmoney said:
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
Click to expand...
Click to collapse
The ROM was updated and the kernel included in the update! Amazing rom , highly recommended especially with the updated kernel!
UPDATE: After a few additional tweaks to the framework, this rom appears to be working for both green and red lens defy users. I've personally used it as my daily driver for several days this week, and found it to be stable and very usable. The one thing that does not work for me is the GPS, and quite honestly, I haven't had time to look in to it.
Here is a complete, working port of PARANOID ANDROID 1.97a for Defy. It is based on Galaxy S2 PARANOID 1.97 and Epsylon's CM10 1208. This is NOT a simple port using the port tool and includes the Framework changes necessary for the hardware.
I take no responsibility for any consequences from your decision to try this rom, and being based on alpha releases, I'm sure there are other problems, but I've personally used this rom for a prolonged period of time and the only problem I've had was with the GPS not locking.
Few things to note:
1. No offense to anyone, but this thread is not for complete noobs. While I will try to help when I can, I cannot promise any level of support. If you don't know how to flash via CWM, this is not for you.
2. This rom is based on the Froyo kernel and has been confirmed to work on MB525 with green as well as red lens. This is no guarantee that it will work on YOUR phone.
3. I intentionally used 1.97 as that version was very stable on my Galaxy Nexus - much moreso than 1.98 or 1.99
4. I've cleared the PARANOID defaults that most of the other PA roms come with. You can manually change the individual app settings under Paranoid Settings, or via the \system\etc\paranoid\properties.conf file which stores a record for every app including DPI and Layout.
5. After installing this rom, I "supercharged" it using a v6supercharger script (link below) and it did seem to help make the rom smoother and more responsive.
Special thanks to Epsylon3 and Quarx for their work on CM10 for the Defy, and Molesarecoming and D4rKn3sSyS for their work on PARANOID.
Thanks to brajesh.sharma87 for pointing out the bootloop "gottcha" of simply recompiling the framework (for specifics google "framework recompile bootloop" and read the first thread that comes up).
I strongly encourage any/all of you to contribute (make donations) to these developers.
DOWNLOAD ROM (double check MD5 before flashing - 96D409B4692319D9DA63FAA9CE1516A6)
Download latest gapps from here.
Here is the v6 supercharger script that I've been using and is confirmed to work with this rom.
Make sure you're on Froyo kernel. Boot in to CWM recovery. Factory reset, wipe data/cache/dalvik. Install rom, followed by gapps. Wipe data/cache/dalvik again. Reboot (should take about 2-5 minutes). Install and configure the v6 script. Enjoy!
Looks pretty neat man! I might give it a shot soon. Any known bugs for now?
This is only PA rom which I manage to get work on my red lens defy without bootloop..
Cheer mate..:good:
now testing..
hm md5 matches, flashed it several times but it cant pass bootanimation :/
(edit: green lense defy)
here tooo stuck at endless bootanim...
o-liver said:
hm md5 matches, flashed it several times but it cant pass bootanimation :/
(edit: green lense defy)
Click to expand...
Click to collapse
meilbox said:
here tooo stuck at endless bootanim...
Click to expand...
Click to collapse
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
dew.man said:
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
Click to expand...
Click to collapse
bro if kernel was wrong they would have stuck at Moto logo not bootanim...
same with my builds too and the reason y i did not update my thread...
I made paranoid too but never boot... libandroid.runtime has errors as per logs...
and m in no mod to fix it for now...
Sent from my MB526 using xda premium
dew.man said:
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
Click to expand...
Click to collapse
did everything what i could, and my led does not flash in red...
nogoodusername said:
bro if kernel was wrong they would have stuck at Moto logo not bootanim...
Click to expand...
Click to collapse
good point.
nogoodusername said:
same with my builds too and the reason y i did not update my thread...
I made paranoid too but never boot... libandroid.runtime has errors as per logs...
and m in no mod to fix it for now...
Click to expand...
Click to collapse
Sorry, didn't even see your thread. Quite honestly, I've only been playing with PA for the last couple of weeks and have posted in rajesh.sharma87 thread as well as the rom porter thread, but nobody over there seems to want to read.
Have you looked at the logs from the devices that loop? Send me one if you have an example. I've tried lots of different combinations in conjunction with the framework-res mods before I got this to boot, but have not had any problems with this version. Interesting...
dew.man said:
good point.
Sorry, didn't even see your thread. Quite honestly, I've only been playing with PA for the last couple of weeks and have posted in rajesh.sharma87 thread as well as the rom porter thread, but nobody over there seems to want to read.
Have you looked at the logs from the devices that loop? Send me one if you have an example. I've tried lots of different combinations in conjunction with the framework-res mods before I got this to boot, but have not had any problems with this version. Interesting...
Click to expand...
Click to collapse
well paranoid jb(gb kernel) no boot for me at all...
havent tried urs m on gb kernel...
i dont have logs m on cm10
i m thinking of setting up git for paranoid... but my internet...:thumbdown:
Sent from my MB526 using xda premium
nogoodusername said:
well paranoid jb(gb kernel) no boot for me at all...
havent tried urs m on gb kernel...
i dont have logs m on cm10
i m thinking of setting up git for paranoid... but my internet...:thumbdown:
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL6 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
dew.man said:
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL7 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
Click to expand...
Click to collapse
How can you be on BL7 and still be able to switch to Froyo kernel?
niksy+ said:
How can you be on BL7 and still be able to switch to Froyo kernel?
Click to expand...
Click to collapse
My bad - it's BL6.
And for those that don't know, there was a leaked Froyo SBF with BL7 (see here).
dew.man said:
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL6 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
Click to expand...
Click to collapse
no the kernel has difference...
gb kernel has many missing libs!
Sent from my MB526 using xda premium
Hi dew.man, if u want to continue this, I will close my thread as u know there's no need of having multiple threads for the same work. The intention of the guide and the tool was to let everyone port and use and not polluting the developement thread by posting so many threads. I hope u get my point. If u really wish to take this up I am there with u and will provide u as much help as I can but at the same time we need to respect xda.
Opinion of other users are also welcome so that we can keep the developement thread clean. I've already closed 2 of my threads for the same reason. LewaOS and AOKP JB.
Sent from my MB525 using xda app-developers app
cant acquire logcat, its waiting for the device :/
o-liver said:
cant acquire logcat, its waiting for the device :/
Click to expand...
Click to collapse
dude goto bootmenu-boot-adb enable
press 2nd-init
and logcat...
Sent from my MB526 using xda premium
brajesh.sharma87 said:
Hi dew.man, if u want to continue this, I will close my thread as u know there's no need of having multiple threads for the same work. The intention of the guide and the tool was to let everyone port and use and not polluting the developement thread by posting so many threads. I hope u get my point. If u really wish to take this up I am there with u and will provide u as much help as I can but at the same time we need to respect xda.
Opinion of other users are also welcome so that we can keep the developement thread clean. I've already closed 2 of my threads for the same reason. LewaOS and AOKP JB.
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
First and foremost, thanks for all your help
Perhaps I was not clear enough, but I do not have the free time to take on any kind of support role. Please understand that my sole intention of this thread, was to provide/share a more recent version of PA/CM10 that I have been unable to obtain from anybody else. No offense intended, but I did ask you on several occasions to post a more recent version than the 1.95 you have in your (still existent) thread, and the only response I received was that you didn't have the bandwidth.
I also tried to work through/with kadevil's thread, but he pretty much ignored all the feedback he was getting about the tool not working for PA and JB.
Again, I was looking for a more recent version of PA (1.97+) with a more recent CM10 (8/06+) and was unable to find a working version. I built one that works for me, and wanted to share with anybody else that may be in a similar position...
Well guys i feel that the thread should be merged to brajesh's thread... since his thread has more organized 1st post...
no offence to op but thats wat i felt when i saw it...
peace
-hackergnome
Sent from my MB526 using xda premium
nogoodusername said:
Well guys i feel that the thread should be merged to brajesh's thread... since his thread has more organized 1st post...
no offence to op but thats wat i felt when i saw it...
peace
-hackergnome
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I'm perfectly fine with that as long as the op/title gets updated with the new version number
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
Q&A for [ROM][OFFICIAL][KitKat 4.4.4][Ville] PAC-ROM 4.4.4.RC-2
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:
atrus5 said:
New build is up. Just some minor changes and fixes to the build. Here is the link. https://s.basketbuild.com/dl/devs?dl=pacman/ville/dev/pac_ville_4.4.4.RC-2_20141019-003708.zip
Click to expand...
Click to collapse
Bluetooth is really broken for me.
Pilipin said:
Bluetooth is really broken for me.
Click to expand...
Click to collapse
Can you send a logcat of what happens when you use Bluetooth
@atrus5 Have you added a custom kernel yet? If not, i'm working on one with @javelinanddart and possibly @AKToronto, but I'd need help compiling it. It always fails for me.
josepha19223 said:
@atrus5 Have you added a custom kernel yet? If not, i'm working on one with @javelinanddart and possibly @AKToronto, but I'd need help compiling it. It always fails for me.
Click to expand...
Click to collapse
I don't add custom kernels to the build. I guess I could but I feel the user can add whatever they want afterwards instead of having one built in. I am not the best person to ask for building a kernel as I don't do that kind of thing. I just like building the roms and testing them.
atrus5 said:
I don't add custom kernels to the build. I guess I could but I feel the user can add whatever they want afterwards instead of having one built in. I am not the best person to ask for building a kernel as I don't do that kind of thing. I just like building the roms and testing them.
Click to expand...
Click to collapse
Well let me know if you want to. you did add a poll so i was just wondering
josepha19223 said:
Well let me know if you want to. you did add a poll so i was just wondering
Click to expand...
Click to collapse
Yeah sorry that poll was from the very beginning of the thread and I can't get rid of it
hello got error flashing Lates PacMan build 4.4.4 pac_ville_KK.RC-3.dev_20141129-123111
E:Error executing updater binary in zip
Click to expand...
Click to collapse
Hboot 2.15, S-off, radio 1.11, TTWRP 2.5.0.0
pls help
upd. Flashing TTWRP 2.8 - fixed problem. Sry for diturbing
BorHblK said:
hello got error flashing Lates PacMan build 4.4.4 pac_ville_KK.RC-3.dev_20141129-123111
Hboot 2.15, S-off, radio 1.11, TTWRP 2.5.0.0
pls help
upd. Flashing TTWRP 2.8 - fixed problem. Sry for diturbing
Click to expand...
Click to collapse
yeah i was gonna say just update your recovery but you got it
Calling out gives blank screen
Hey - new to the forum here, and I know this rom is discontinued for the ville, but perhaps someone can point me in the right direction;
When I want to place a call, the screen goes blank. The call itself is being made, but I cannot get the screen to work again. Even after the call disconnects. Only way, is to lock screen with power button (still blank) and press power button again to go to unlock screen.
This problem is also for incoming calls only after picking up the phone.
This is what I did to the phone so far:
- Unlock bootloader via HTC site
- Root phone
- Install TWRP
- Flash PACROM , PA GApps, Update-SuperSU, flash boot.img in fastboot
My setup:
HTC One S S4
HBOOT 2.15
Radio: 1.11.50.05.28_10.27.50.08L
Kernel: 3.4.82
ROM: pac_ville 4.4.4 20141231
S-ON
TWRP: 2.8.6.4
SuperSU 2.46
I have looked around in the threads here but seems no-one else is having this problem.
Can you try to use a different gapps. Pa adds info to there gapps. Use the gapps from the op.
Actally it was the proximity sensor that was giving issues, I used a calibration app to set it manually and since have been using Pacman happily. God it would be great to see a LP PACMAN for the Ville
krillin2112 said:
Actally it was the proximity sensor that was giving issues, I used a calibration app to set it manually and since have been using Pacman happily. God it would be great to see a LP PACMAN for the Ville
Click to expand...
Click to collapse
Glad you found the problem and fixed it.
It won't be me making the build. If anyone else wants to that would be great.
Sent from my Nexus 5 using XDA Forums
Yeah I read you no longer have a working Ville. I really do like the ROM and maybe one day someone can make a LP build. There is one for the HTC One (m7 & m8). Don't know how much work it would entail to adapt that to Ville.
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure