Develop Bugs

[Q] MoKee random reboots

Hi everyone!
I'm using the latest MoKee MK44 ROM for our Ace.
I really like this ROM but there seems to be a problem with the kernel. It reboots randomly during read or write processes.
Does anybody know something to fix that problem?
I attached the last_kmsg, maybe you can tell me whats going wrong here.
EDIT: It seems that it's not MoKee causing this problem.
EDIT2: I got a solution for the problem, take look at this post.

I haven't experienced that....but if I were to,I would definitely just clean flash ROM again.

I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!

Does really nobody knows something about the last_kmsg? Here are so many professionals and none of you can help?
Attached another last_kmsg, I took it right after a reboot.
Pulled battery, booted to recovery and copied it so I think there aren't many non-relevant events at the end of the file.
Attached file is now zip, maybe you don't like rar, I don't know. Thanks

Vega Bullet said:
I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!
Click to expand...
Click to collapse
No reboots here

marknoll said:
No reboots here
Click to expand...
Click to collapse
:good:
Ok, tried clean flashing once again, still the same result.
So what about the last kmsg?

What recovery are you using?

marknoll said:
What recovery are you using?
Click to expand...
Click to collapse
TWRP 2.7.1.0
Used the latest 4ext before that but had some problems, so I changed to twrp which works better I think.

Use the mod twrp jriors... That flashes everything.

marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
So you think it's a flashing problem? Like I said, I think there were no problems (especially random reboots) with other ROMs, that's why I didn't thought it's a flashing problem. But I will try it again.
EDIT: Can you give a link? Would help me saving some time

http://forum.xda-developers.com/showthread.php?t=2780164&page=4

marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
marknoll said:
http://forum.xda-developers.com/showthread.php?t=2780164&page=4
Click to expand...
Click to collapse
Well...
Vega Bullet said:
TWRP 2.7.1.0
Click to expand...
Click to collapse
I didn't know if "jriors" one is a special version but that is exactly the recovery I am using.
I got it from that thread, not from the mirror on page 4 you linked me to but from his first post.
So this would not change anything. Please correct me if I'm wrong.

All I can say is that maybe u got a bad download. Redownload the ROM and check md5. Then flash it with jriors. Should work fine then

Ok, looked for the checksums, matched.
And again, does really nobody know anything about the kernel log file? No idea? No clues?
I'm testing latest CM11 once again, maybe I find something...
EDIT: Tested under same conditions. Same problem with CM11. So I think an app or setting is causing it.
Would be very helpful if someone can take a look into kernel log.

My advice is to factory reset from recovery. Then go under advanced wipe and chose cache, dalvik,android secure and system wipe. Then flash the ROM and gapps..reboot after and let it run before logging in play store or installing any apps
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
[/COLO
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Can I plz have the link you're getting this ROM from? I think that maybe ur downloading an incompatible rom

I'm sure I do the procedures correct, tried simple factory reset (with recovery) and additionally wipe /system and android secure too.
Download ROM from here, look for checksums, flash boot.img separately.
But now, even if I only use it like it's been flashed, I'm getting reboots. Not only reboots. It seems that everything isn't correct.
Freshly flashed, want to reboot device normally but hangs during reboot dialog or bootloops...
Currently I'm testing the first ROM flashed the DHD with, CM11 OnePlusOne Edition and
THAT Rom seems to work. No reboots, hangs or bootloops, very confusing...
So it's getting very difficult to help me, no pattern I can follow to get out what's wrong
I thought Titanium Backup was the problem but like I said, even if it's clean it doesn't work.
Well, I will test everything again, let's see.

Are you s off?

marknoll said:
Are you s off?
Click to expand...
Click to collapse
No, thought of it but I was to lazy to read me through all the things I have to do,
flashing original ROM and what I have to keep in mind and so on...
Maybe I will try it but my time is also limited.
In the last_kmsg you can read that right after "rebooting in 5 seconds" there is "BUG: scheduling while atomic: htc_ebdlogd..."
I simply deleted the file htc_ebdlogd (because I don't know what else to do) and rebooted, seems to be no problem without that.
Till now the problem does not occurred. Till now..

Same problem on CM11 M9?
I think I'm having the same problem with CM11 on my Ace. I installed it this afternoon and have had random reboots on multiple occasions. Can't find a pattern for when it occurs. I don't have a logcat log from when it happens yet, but I'll try to obtain one.
My phone is S-ON (only HTCDev unlocked) and I used the TWRP 2.7.1.0 from [1], the CM11 M9 build from [2] and the PA GApps Modular Nano package from [3]. I installed by:
In TWRP:
1) Wipe (should wipe everything right?)
2) Install CM11 zip
3) Install PA GApps zip
Then flashed the extracted boot.img from fastboot.
I'd be very interested in hearning if deleting htc_ebdlogd really worked for you Vega Bullet.
Cheers,
Elvis
[1] http://forum.xda-developers.com/showthread.php?t=2780164
[2] http://forum.xda-developers.com/showthread.php?t=2533007
[3] http://forum.xda-developers.com/showthread.php?t=2397942

The kernel log is located under /proc named last_kmsg
For now it works fine let's but I don't really know if there are any consequences nor if it works.
EDIT: After a few days of testing a can say there are no reboots anymore, I am using MoKee MK44 for Ace and it's working fine.
Although I still don't know about consequences I can't say there are any but you do it without warranty.
So if you experience the same error
(means random reboot,
look into /proc/last_kmsg,
you should see the line "BUG: scheduling while atomic: htc_ebdlogd..."),
make a nandroid and delete htc_ebdlogd (should be located in /system/bin).
Btw, looking at the MoKee Source I only see one reference to this binary, it's located under ramdisk/init.spade.rc .
Maybe someone know's more and what it's good for, like I said without it I don't see differences...

[Q&A] [ROM][4.2.2][UPDATED][THEMED][GT-I9082] XperiaZ Flavor To Galaxy Grand Duos

Q&A for [ROM][4.2.2][UPDATED][THEMED][GT-I9082] XperiaZ Flavor To Galaxy Grand Duos
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][4.2.2][UPDATED][THEMED][GT-I9082] XperiaZ Flavor To Galaxy Grand Duos. 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!

No bootloader or boot logo
Ok. First while wiping factory data and wipe dalvik, it showed "unknown volume for path /sd-ext". I ignored because it was also shown when i flashed stock ROM.
Then after flashing rom, during rebooting, an error came: "rom may flash stock recovery on boot - select yes to keep recovery". I select yes.
Then While i Odex the ROM using odex -all, there are many failed to odex messages.
Also there is no boot logo is coming and there is no xperia lock screen and its just theme like not really which is shown in video.

shantam22 said:
Ok. First while wiping factory data and wipe dalvik, it showed "unknown volume for path /sd-ext". I ignored because it was also shown when i flashed stock ROM.
Then after flashing rom, during rebooting, an error came: "rom may flash stock recovery on boot - select yes to keep recovery". I select yes.
Then While i Odex the ROM using odex -all, there are many failed to odex messages.
Also there is no boot logo is coming and there is no xperia lock screen and its just theme like not really which is shown in video.
Click to expand...
Click to collapse
In this rom there is no Boot logo, if u want u can put it by yourself & for the lock screen is same as stock only background change not the unlocking type.
this just a flavored from
for lock screen check theme http://forum.xda-developers.com/showthread.php?t=2283514] [MOD]%20[GT-I9082]%20Dual%20SIM%20Icon%20Removed%20From%20Notification%20Pulldown[/url]%20-%20by%20balliboxer%3Cbr%20/%3E%3Cbr%20/%3E[url=%22http://forum.xda-developers.com/showthread.php?t=2285707
or
u can download it from playstore

Sunil Jagtap said:
In this rom there is no Boot logo, if u want u can put it by yourself & for the lock screen is same as stock only background change not the unlocking type.
this just a flavored from
for lock screen check theme http://forum.xda-developers.com/showthread.php?t=2283514] [MOD]%20[GT-I9082]%20Dual%20SIM%20Icon%20Removed%20From%20Notification%20Pulldown[/url]%20-%20by%20balliboxer%3Cbr%20/%3E%3Cbr%20/%3E
Hey thanks for reply.
Also during the command in terminal, "dexo -all". There are several errors : failed to odex. and during the process, many app not responding errors.
---------- Post added at 10:42 AM ---------- Previous post was at 10:22 AM ----------
During the command in terminal, "dexo -all". There are several errors : failed to odex. and during the process, many app not responding errors. And LMT is giving ANR error
Click to expand...
Click to collapse

shantam22 said:
Hey thanks for reply.
Also during the command in terminal, "dexo -all". There are several errors : failed to odex. and during the process, many app not responding errors.
---------- Post added at 10:42 AM ---------- Previous post was at 10:22 AM ----------
During the command in terminal, "dexo -all". There are several errors : failed to odex. and during the process, many app not responding errors. And LMT is giving ANR error
Click to expand...
Click to collapse
Try from first step & Clean install (wipe all data, cache & Dalvik also)
Don't say thanks hit it

Problem installing
Sunil Jagtap said:
Try from first step & Clean install (wipe all data, cache & Dalvik also)
Don't say thanks hit it
Click to expand...
Click to collapse
Hey, I have already tried fully cleaned install of the rom. I flashed latest stock 4.2.2 then install custom recovery then install this xperiaz.zip. But same problem.
Is it possible that it is due to me installing it over latest stock rom. Should I install a older version of 4.2.2 stock rom and then retry.

shantam22 said:
Hey, I have already tried fully cleaned install of the rom. I flashed latest stock 4.2.2 then install custom recovery then install this xperiaz.zip. But same problem.
Is it possible that it is due to me installing it over latest stock rom. Should I install a older version of 4.2.2 stock rom and then retry.
Click to expand...
Click to collapse
no need to be, u can install on any version

Anyone having same problem?
Sunil Jagtap said:
Try from first step & Clean install (wipe all data, cache & Dalvik also)
Don't say thanks hit it
Click to expand...
Click to collapse
Sunil Jagtap said:
no need to be, u can install on any version
Click to expand...
Click to collapse
HEy thanks for helping.
Is anyone having the same problem? Several Failed to odex error, No change in settings(same as stock 4.2.2), It just installed some apps like album, movies, walkman and color is black, etc., else things are same as stock 4.2.2

shantam22 said:
HEy thanks for helping.
Is anyone having the same problem? Several Failed to odex error, No change in settings(same as stock 4.2.2), It just installed some apps like album, movies, walkman and color is black, etc., else things are same as stock 4.2.2
Click to expand...
Click to collapse
Why do you need to odex???
Do all the appearances as shown in the original thread match as in your phone?

Problem installing ROM.
NoobInToto said:
Why do you need to odex???
Do all the appearances as shown in the original thread match as in your phone?
Click to expand...
Click to collapse
No. There are several errors. LMT stops responding. setting menu is unchanged, just like stock. And carousel view is not working.
And Hey, I am getting this error while wiping data and dalvik cache: "unknown volume for path /sd-ext". I looked up the forum and thinking that it might be problem in partition. Should I repartition my storage. If yes, then please tell how.

Do this. Do a factory reset from recovery. Then reinstall this rom. Make sure you don't get any errors while reflashing the zip.

FM Radio is missing!
FM Radio is missing in the rom. Please can provide that.

[Q&A] [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]

Q&A for [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]
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 [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]. 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!

Hi guys I did try it on my p601 and its ecelent
thought its easy just exported my modem on old p601 and tried to import it but I didnt make the trick
some other developer did mods for p601 then p600 maybe they can give a hint what else need to be done on a p601
ACTUALLY I use xkat 2.0 that developer did first an p601 and downgraded then a p600 version
would have no issue to use my device as p600 but get only internet by 3g

To get 3g to work requires a new device tree you can't just import your modem there will be a lot of files that need to call specific hard ware files, etc to get the 3g to work. I wish it was as simple as that
Sent from my SM-N9005 using Tapatalk

Does this Rom Have any Spen Support? Can anyone confirm?

cm12 how do i remove the mouse cursor?
As the question really. I am an artist and need to remove the onscreen mouse cursor when spen is used. I don't use an external mouse so dont mind losing it entirely.
Any ideas how?
Many thanks

My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?

WILDrBEAST said:
My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?
Click to expand...
Click to collapse
I don't have the camera issue,i dirty flashed like you are intending to.

Dirty flashing will fix the camera issue as in dirty flashing guy rom over raymanfx build or the nexus experience ... Some reason from source code the camera is not working. I want to build regular cm to check what portion I am missing (if any) of correct sources. I know what the error is from the logs however I fix one part and another crops up so I think there is something missing
Sent from my SM-N9005 using Tapatalk

Thanks!
I also think that this rom ir best of best.

Can anyone confirm pressure sensitivity is working? I cant find an answer, I read that spen is only a pointer so that does not work for drawing apps that use pressure?

My P600 came FedEx today and I'm ready to root and flash.
Should I update the device from P600UEUCNI1 to P600UEUCNK2 to get the latest KK recovery before I start? (if the 2 newer updates even makes changes to recovery).
I am getting the update prompt though it doesn't say which build.

The recovery shouldn't matter it will get flashed over with a twrp build anyway...
I am not up to date on the root ability of the newest bootloader as my device was rooted when I got it stock and I don't recall updating bootloader at any stage
Sent from my SM-N9005 using Tapatalk

problem when flashing
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault

patrykket said:
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault
Click to expand...
Click to collapse
Sounds to me that you are having problem with twrp recovery I had this when flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk

joshndroid said:
Sounds to me that you are having problem with twrp recovery I had this whdden flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
Click to expand...
Click to collapse
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]

patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]
Click to expand...
Click to collapse
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/

joshndroid said:
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/
Click to expand...
Click to collapse
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.

patrykket said:
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.
Click to expand...
Click to collapse
Please re-read my previous post.
I did not say manually flash rom, i was talking about the RECOVERY which is the TWRP recovery by using ODIN.
Please have a good read through guides, if the ones i linked don't help you try googling, there are plenty others. There are videos on youtube showing how to flash files/recovery using odin.
Please read as much as you can before starting, because when it goes bad no one is going to be able to fix it for you. As much as it is at your own risk i wouldn't like to see someone's hard earned money turn into a paperweight.

Tell me please, working s-pen?

The GPS is not working for me on this rom, heres what I did...
Step 1:
I flashed TWRP 2.6.3.3 with Odin 3.10,
Made a backup with TWRP,
Cleared Cache,
Cleared Dalvik,
Cleared Data,
Flashed cm-12-20141205,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Step 2:
Flashed cm-12-20141218,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Made a backup with TWRP,
Step 3:
Flashed cm-12-20150104 v4.2,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test does not work, neither does Navigation
Also tried "Step 3" with cm-12-20150103 v4.0 AND cm-12-20141231 v3.8 with the same result.
THIS ROM ROCKS! VERY SMOOTH AND FAST!!
Could this be a simple fix? did I take any incorrect steps?

[Q&A] [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-

[Q&A] [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-
Q&A for [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-2015
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][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-2015. 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!

negamann303 said:
You need to be on nk1 firmware and use Cwm recovery
Click to expand...
Click to collapse
My tab was completely stock till today, all i did was root it and flash this

(No longer relevant)

TWRP question?
Hi all, Just wanted to give a big thanks for the work being done on this. I thought it was going to be washed up but it has been
revived ! Thanks again
Now here is what I'm wondering.
After taking the NK1 firmware, I rebooted and Odin the recovery from #2 TWRP
- Noticed in the new recovery it has a message that says "E:unable to mount / firmware" and "E: error sending message to add(or remove) storage 65537" . Is there something else I should be clicking on more?
I basically flashed the ROM as I normally would when I was running the older version of TWRP for a clean install.
I was wondering if all this is normal or did something fail to install when I did my Odin?
thanks again and like I said so far its been running great !!
Z.

Hey guys I cant get my wifi to turn on after clean install

kashis32 said:
Hey guys I cant get my wifi to turn on after clean install
Click to expand...
Click to collapse
Did you double check ur firmware? I upgraded 2 NK1 @ first but only 2 of the 4 (pda csc) updated and the baseband and bootloader didn't @ first. Had to Odin back over again now all r NK1. I use the Samsung phone info app to double check. Try that and make sure u do a full clean install. Well that's what worked 4 me.
Z.

Any update on broken wifi? i am on nk1 so idk why it doesn't work.

zsibisi said:
- Noticed in the new recovery it has a message that says "E:unable to mount / firmware" and "E: error sending message to add(or remove) storage 65537".
Click to expand...
Click to collapse
I have the same errors... So far it doesn't seem like it has affected anything though. The only issue I have is the battery seems to drain a lot faster than on stock nk1.
This is actually my first time flashing a rom so idk if maybe it was one of the options I checked in the beginning or not. I chose the unsecured adb kernel so maybe I'll try the stock kernel and see if the errors or battery thing change because I don't really know what the difference between them is.
---------- Post added at 05:17 PM ---------- Previous post was at 05:09 PM ----------
Tijaun said:
Any update on broken wifi? i am on nk1 so idk why it doesn't work.
Click to expand...
Click to collapse
Hey like I said in my other post this is the first time I've flashed a rom so I don't know much. But when I started this I had to flash stock nk1 and apparently I flashed the wrong version because my wifi wouldn't work even in stock so I then flashed a different stock nk1 and everything worked and continued to work when I flashed this rom.
So what I'm trying to say is maybe you need to flash a different stock nk1 again and see if that works?

Any thoughts on improving battery life? Seems stock had better performance than this ROM. Other than that i love this ROM and will keep it as my daily driver. Buttery smooth and no force closes.
late,
Coz

cozboogie said:
Any thoughts on improving battery life? Seems stock had better performance than this ROM. Other than that i love this ROM and will keep it as my daily driver. Buttery smooth and no force closes.
late,
Coz
Click to expand...
Click to collapse
Try deleting /etc/init.qcom.post_boot and restarting. That's where most of my performance tweaks are. If it saves battery, let me know.
As for recovery. The /firmware mount error doesn't matter. TWRP is the only recovery that doesn't recognize it. I'll just comment it out for next release (already using TWRP 2.8.4.0 on my tablet [emoji14])
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so

negamann303 said:
Try deleting /etc/init.qcom.post_boot and restarting. That's where most of my performance tweaks are. If it saves battery, let me know.
As for recovery. The /firmware mount error doesn't matter. TWRP is the only recovery that doesn't recognize it. I'll just comment it out for next release (already using TWRP 2.8.4.0 on my tablet [emoji14])
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so
Click to expand...
Click to collapse
Deleted suggested file....device "feels" snappier....I'll keep an eye on battery life.
late,
Coz

negamann303 said:
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so
Click to expand...
Click to collapse
When I flashed the rom it gave two options for the kernel one said something like "nega unsecured adb" the other said "completely stock". I figured the one that said nega was you're kernel and the other was the tablets stock? Am I wrong on that and what is the difference between them?

Level47 said:
When I flashed the rom it gave two options for the kernel one said something like "nega unsecured adb" the other said "completely stock". I figured the one that said nega was you're kernel and the other was the tablets stock? Am I wrong on that and what is the difference between them?
Click to expand...
Click to collapse
The version in the Rom just has an edited ramdisk for unsecured adb is all

@negamann303: Thank you for a fantastic rom. It's great to see some renewed interest in the T217S. I discovered it last night, read through both threads, updated firmware first and then flashed your TWRP, rom and themes. Everything is running smoothly. Looking forward to your TWRP update just to hide those firmware error messages.

I had this problem after flashing the recovery zip. Tried both TWRP and Philz with both reporting thd same.
Next question, how do change air gesture options. I made some changes when I turn the option on. Now I can not find Motion or any option in settings to edit or change. What am I missing? ???????

So I just flashed the new recovery and the firmware error is gone but when I flashed timberwolf's theme (atleast I think it was after the theme but I definitely got the error) I still got the "E:error sending message to remove storage 65537" error. But after a quick Google it turns out you have to turn off mtp in the recovery to fix this issue.
The twrp thread here on xda explains it and also tells you how to disable mtp in twrp.
http://forum.xda-developers.com/showpost.php?p=58224851&postcount=102
wingman358 said:
When you first enter recovery, go to the "Mount" menu then on the lower right side it should say "Disable MTP". Click it to disable and you shouldn't get the error if you go and wipe after doing that.
It's not persistent so you'll have to do it each time you restart the recovery and want to do a storage wipe.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse

Okay, so I guess I haven't been following this thread as closely as I thought. I didn't realize we were at v2. Downloading now. Can I dirty flash? Any plans to use SVN? If I need to do a clean flash, I will then have to re flash the kernel and theme, right? I remember SVN was a life saver before because Nega is like a mad scientist....always tinkering. Also, I have never learned how to back everything up for clean flashes. Do I go they the whole setup every time like a pilgrim. Titanium bckup is mystifying to me.

GAPO said:
Okay, so I guess I haven't been following this thread as closely as I thought. I didn't realize we were at v2. Downloading now. Can I dirty flash? Any plans to use SVN? If I need to do a clean flash, I will then have to re flash the kernel and theme, right? I remember SVN was a life saver before because Nega is like a mad scientist....always tinkering. Also, I have never learned how to back everything up for clean flashes. Do I go they the whole setup every time like a pilgrim. Titanium bckup is mystifying to me.
Click to expand...
Click to collapse
If you are using Titanium Backup Pro, I created a screencast video for my phone that shows the right way to create an update.zip file that you can flash from recovery immediately after doing a clean install. I also tried it on my Tab 3 with no problems.

Ramer said:
If you are using Titanium Backup Pro, I created a screencast video for my phone that shows the right way to create an update.zip file that you can flash from recovery immediately after doing a clean install. I also tried it on my Tab 3 with no problems.
Click to expand...
Click to collapse
Thanks! A couple of questions...when I apply the update.zip, will it have trouble re installing apps that I got from sources other than Google Play store? I mean, is it storing the apps to re install from the zip, or re-downloading them from the play store? Because I got some of mine from other sources.

GAPO said:
Thanks! A couple of questions...when I apply the update.zip, will it have trouble re installing apps that I got from sources other than Google Play store? I mean, is it storing the apps to re install from the zip, or re-downloading them from the play store? Because I got some of mine from other sources.
Click to expand...
Click to collapse
No trouble at all. It's creating the update.zip from the apps that you chose to backup, their coming from your phone tablet, not the Playstore.

[Q&A] [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1

Q&A for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1
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][CM-12.1][Un-official] D2SPR CyanogenMod 12.1. 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!

Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.

bmx26 said:
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
Click to expand...
Click to collapse
Inside of drive, Try long pressing on it and clicking "download copy" it should download a copy to the downloads folder on your internal sdcard

using this rom cm12.1 for s3 sprint and its working great so far, only noticed two things........ camera not working and Battery but im going to see after a day or two if the battery last the same as the previous rom i was on cm12 (camera was working sort of with the camera zoom fx and viva video work around but i used high speed camera plus instead of camera zoom fx with viva video and it was good)............. so cant wait for a working camera or some kind of work around for this rom cm12.1 s3 sprint.......

Silly mod question.
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.

brad2512 said:
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
Click to expand...
Click to collapse
The google drive link has the file

Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.

Brisky86 said:
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Click to expand...
Click to collapse
it might. I was reading about some commits on github that broke cameras across the board, stock or from the play store. I tear laptops apart regularly enough to remember how, it's the process itself that sucks

After messaging mastamoon, "I imagine all the stuff that's being worked on is basically in d2-common, msm8960-common and d2kernel which d2spr shares with d2vzw. I would just make sure whoever is building for d2spr is pulling in all the necessary hacks needed at the moment. Honestly I'm not sure what isn't committed at this point, but check out commits by Dave Daynard (nardholio) & Dan Pasanen (invisiblek) and make sure you're using that stuff."
The kernel (within this ROM) he's speaking of might help with the issues revolving around the camera.

Camera Works
Just thought I'd say that both cameras work all the time for me on the 4/09 build.

You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Good to know thank hou
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
ChangeOfJinzo said:
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
Click to expand...
Click to collapse
Make sure you have the latest cwm recovery and you should be fine. I'd recommend flashify, I liked it better and seemed to function better then twrp manager. Also once you install twrp there's a method to update the recovery without a computer or making a recovery updater zip, which can also flash custom kernels. Though I recommend sticking with the stock kernel untill cm12.1 becomes more stable

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can anyone else confirm? I've yet to get this build in particular to boot...

iBlowpot said:
Can anyone else confirm? I've yet to get this build in particular to boot...
Click to expand...
Click to collapse
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)

ChangeOfJinzo said:
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
Click to expand...
Click to collapse
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.

iBlowpot said:
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
Click to expand...
Click to collapse
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.

Lrs121 said:
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Click to expand...
Click to collapse
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.

iBlowpot said:
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
Click to expand...
Click to collapse
Probably a bad upload. I recommend using the new build.
FatalIll said:
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
Click to expand...
Click to collapse
also what bootloader and firmware version

Lrs121 said:
also what bootloader and firmware version
Click to expand...
Click to collapse
Hell, just give us your phone
Also, Lrs121... You had mentioned that you may try and cherry pick updates from other builds where the camera is working. I don't know much about cm source or building but have you considered using something like 'kaleidoscope git diff' to compare builds and see maybe where the camera fix is hiding?
Edit: not necessarily kaleidoscope, but git diff in general.