Q&A for [ROM][4.4.4][Unofficial] Carbon KitKat - Togari[2014-10-18]
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:
NFC not functional
On my Z Ultra, the NFC service seems to use a lot of battery. I went into settings to turn it off, but upon touching, it went grey but still ticked. Leaving that screen and going back into it reveals the NFC still ticked but not grey. Having to remove NFC service to prevent battery drain. Also, even NFC being on doesn't work with tags or anything. Any suggestions? Thanks heaps
Problem with sensors
Accelerometer, light, orientation, proximity, gyroscope and magnetic sensor no longer work on latest carbon (build 33)
Is there anyone else with the same problem?
Hilmhaz said:
Accelerometer, light, orientation, proximity, gyroscope and magnetic sensor no longer work on latest carbon (build 33)
Is there anyone else with the same problem?
Click to expand...
Click to collapse
I had the same problem on LiquidSmooth built from source. A build from around 26 September worked fine, so it seems there's something later than that causing it. I tried reverting some commits related to sensors, but was unable to find the cause of the issue. Maybe @OmarEinea knows. Someone reported it in PAC's thread on the Z1 forum, too. I also had to revert the latest media-caf-new commits to even get through the build using the SaberMod toolchain. Back to earlier builds for now, but it's still awesome.
Triflot said:
I had the same problem on LiquidSmooth built from source. A build from around 26 September worked fine, so it seems there's something later than that causing it. I tried reverting some commits related to sensors, but was unable to find the cause of the issue. Maybe @OmarEinea knows. Someone reported it in PAC's thread on the Z1 forum, too. I also had to revert the latest media-caf-new commits to even get through the build using the SaberMod toolchain. Back to earlier builds for now, but it's still awesome.
Click to expand...
Click to collapse
There was a few updates from themuppets that may have broken things
blueether said:
There was a few updates from themuppets that may have broken things
Click to expand...
Click to collapse
Good call! Thanks!
This is the commit that broke sensors for me. I'll try a CM11 nightly later and try to report the issue if it's present there.
Any chance that the sensors may be fixed soon? It's pretty inconvenient atm.
341464 said:
Any chance that the sensors may be fixed soon? It's pretty inconvenient atm.
Click to expand...
Click to collapse
I'm away for the weekend so cant look into it. My only suggestion is to roll back to the backup you made befor flashing or to flash an older build (if you flash an older build you will probably need to wipe data)
blueether said:
I'm away for the weekend so cant look into it. My only suggestion is to roll back to the backup you made befor flashing or to flash an older build (if you flash an older build you will probably need to wipe data)
Click to expand...
Click to collapse
I just got this device literally 12 hours ago, so no previous backup exists. Flashed Carbon immediately I got the device and probably chose a wrong time.
I can wait though, since I had spent hours setting the device up, don't really wanna do it all over again.
341464 said:
I just got this device literally 12 hours ago, so no previous backup exists. Flashed Carbon immediately I got the device and probably chose a wrong time.
I can wait though, since I had spent hours setting the device up, don't really wanna do it all over again.
Click to expand...
Click to collapse
Carbon build 32 should be fine (problem only with bluetooth) but build 30 and earlier is recommended if Bluetooth is a must.
I did dirty flash build 32 on top of build 33 and it somehow work, but not recommended
Hilmhaz said:
Carbon build 32 should be fine (problem only with bluetooth) but build 30 and earlier is recommended if Bluetooth is a must.
I did dirty flash build 32 on top of build 33 and it somehow work, but not recommended
Click to expand...
Click to collapse
I'd rather wait for a new build, unless it isn't fixed in 2 weeks.
EDIT: Actually, wait, can't I just replace the sec_config with the older one?
EDIT 2: Yup, fixed by replacing the sec_config with the older one.
No problem now.
Is there a way I can change how "exact" or sensitive dt2w is? I can only get it to work for me every other time...I don't know if I am tapping to far from the other tap or what...I swear I am tapping in the same spot twice
KaBooMa said:
Is there a way I can change how "exact" or sensitive dt2w is? I can only get it to work for me every other time...I don't know if I am tapping to far from the other tap or what...I swear I am tapping in the same spot twice
Click to expand...
Click to collapse
You cant change the way dt2w works sorry
Thanks for the reply. I have been sitting here training lol....I think I got it figured out finally. I was just doing some weird stuff and it wasn't working.
any updates?
This rom is rip?any information about next updates?
kowkin said:
This rom is rip?any information about next updates?
Click to expand...
Click to collapse
The Carbon team have mostly moved on to LP, i'm just waiting for it to build and boot cleanly then there will be a LP lelease
Related
Here is a thread for the official CM10.1.
Here is where to get it
http://get.cm/?device=tf201
demercie said:
Here is a thread for the official CM10.1.
Here is where to get it
http://get.cm/?device=tf201
Click to expand...
Click to collapse
come on guys animate this thread,news about autorotation?
---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------
pit84 said:
come on guys animate this thread,news about autorotation?
Click to expand...
Click to collapse
demercie this thread is a good idea because alle the guys post on the unofficial builds threads when i have a news about the mayor fix of the nightly i post here thanks
I've been running the last of the UNofficial 10.1 nightlies, dated May 22. Other than no autorotation, it seems to run just fine. Once the Official nightlies started a few weeks ago, I jumped in and flashed a few, up to the 0629 nightly. In addition to the autorotation issue, suddenly my dock battery is not recognized, and I have (apparently already known) issues where both external SD cards are not recognized, on the device or in Windows. Checking the changelogs, I note that there have been HUGE changes/additions in the last few nights, so I figured I'd try the July 4 nightly. BIG effing mistake, UI crashes immediately, multiple error mesages, and I could barely get back to TWRP to restore my faithful 0522 Unofficial.
Thoughts on why the unofficial build works fine, but the "official" ones don"t? What could I be doing wrong?
Thx...
jp071848 said:
I've been running the last of the UNofficial 10.1 nightlies, dated May 22. Other than no autorotation, it seems to run just fine. Once the Official nightlies started a few weeks ago, I jumped in and flashed a few, up to the 0629 nightly. In addition to the autorotation issue, suddenly my dock battery is not recognized, and I have (apparently already known) issues where both external SD cards are not recognized, on the device or in Windows. Checking the changelogs, I note that there have been HUGE changes/additions in the last few nights, so I figured I'd try the July 4 nightly. BIG effing mistake, UI crashes immediately, multiple error mesages, and I could barely get back to TWRP to restore my faithful 0522 Unofficial.
Thoughts on why the unofficial build works fine, but the "official" ones don"t? What could I be doing wrong?
Thx...
Click to expand...
Click to collapse
Did you wipe before installing? I know its CM to CM but like you said there have been lots of changes. If it still crashes then it's probably effed for the moment.
jp071848 said:
I've been running the last of the UNofficial 10.1 nightlies, dated May 22. Other than no autorotation, it seems to run just fine. Once the Official nightlies started a few weeks ago, I jumped in and flashed a few, up to the 0629 nightly. In addition to the autorotation issue, suddenly my dock battery is not recognized, and I have (apparently already known) issues where both external SD cards are not recognized, on the device or in Windows. Checking the changelogs, I note that there have been HUGE changes/additions in the last few nights, so I figured I'd try the July 4 nightly. BIG effing mistake, UI crashes immediately, multiple error mesages, and I could barely get back to TWRP to restore my faithful 0522 Unofficial.
Thoughts on why the unofficial build works fine, but the "official" ones don"t? What could I be doing wrong?
Thx...
Click to expand...
Click to collapse
yes,well i have this bug in my official nightly but is really soon for a stable build and the developers release one build for day let them operate.i think 1 or 2 moins and the big issues are solved
shuwoo said:
Did you wipe before installing? I know its CM to CM but like you said there have been lots of changes. If it still crashes then it's probably effed for the moment.
Click to expand...
Click to collapse
Sort of. I did do a number of cache wipes, but I admit I never did do a full wipe/ factory reset. I also note on other forums that the early July Nightlies are causing others some of the same crashes I saw, so I guess I'm not alone. We'll have to be patient
Aren't the Unofficial builds a port of the TF300 or TF700 builds? It would definitely account for the fact we're starting all over with features on the nightly builds as this would be a completely new tree starting from the ground up on inclusion of feature sets as the build comes together.
Been running the nightly for a few days now and it's been just fine for me. Of course, I did start off the entire 10.1 journey with a total wipe first.
BUILD cm-10.1-20130701-NIGHTLY-tf201
A couple obvious missing features to point out for those who may be just getting to this:
Auto-rotate not working
Dock/Keyboard battery not recognized
Function buttons on the keyboard not recognized (obviously)
Loading up the 0706 Nightly right now so I'll run through the motions later and give a more detailed outline of things I notice.
---------- Post added at 10:22 AM ---------- Previous post was at 09:43 AM ----------
OK, cm-10.1-20130706-NIGHTLY-tf201 should be avoided.
When it comes up it immediately starts throwing System UI failures. Had to force power off and go into recovery mode in order to gain control.
Last known good for me was cm-10.1-20130701-NIGHTLY-tf201 so I rolled back to that from TWRP. Considering it's reported that this issue appears on the 0704 as well, I figured it was safest to go back that route for now.
I think I'll give it a few days before trying another build and just keep an eye on the builds to see if anything significant changes to resolve this.
For now, 20130701 is the most stable that I'm aware of. Perhaps someone else can chime in if they are running anything newer successfully.
tsvortex said:
Aren't the Unofficial builds a port of the TF300 or TF700 builds? It would definitely account for the fact we're starting all over with features on the nightly builds as this would be a completely new tree starting from the ground up on inclusion of feature sets as the build comes together.
Been running the nightly for a few days now and it's been just fine for me. Of course, I did start off the entire 10.1 journey with a total wipe first.
BUILD cm-10.1-20130701-NIGHTLY-tf201
A couple obvious missing features to point out for those who may be just getting to this:
Auto-rotate not working
Dock/Keyboard battery not recognized
Function buttons on the keyboard not recognized (obviously)
Loading up the 0706 Nightly right now so I'll run through the motions later and give a more detailed outline of things I notice.
---------- Post added at 10:22 AM ---------- Previous post was at 09:43 AM ----------
OK, cm-10.1-20130706-NIGHTLY-tf201 should be avoided.
When it comes up it immediately starts throwing System UI failures. Had to force power off and go into recovery mode in order to gain control.
Last known good for me was cm-10.1-20130701-NIGHTLY-tf201 so I rolled back to that from TWRP. Considering it's reported that this issue appears on the 0704 as well, I figured it was safest to go back that route for now.
I think I'll give it a few days before trying another build and just keep an eye on the builds to see if anything significant changes to resolve this.
For now, 20130701 is the most stable that I'm aware of. Perhaps someone else can chime in if they are running anything newer successfully.
Click to expand...
Click to collapse
Thanks for the confirmations. And yes, as you indicate, the Unofficials are built on the TF700. I did a complete wipe/reset etc and then tried the 0701 that seems to work fine, but I ran into the same problems. In addition to the three issues noted above, I continue to have no access to either of the external SD cards, which for me is a show-stopper. I'll have to stick with the 0522 Unofficial for a while, at least it's fully functional for me..
jp071848 said:
Thanks for the confirmations. And yes, as you indicate, the Unofficials are built on the TF700. I did a complete wipe/reset etc and then tried the 0701 that seems to work fine, but I ran into the same problems. In addition to the three issues noted above, I continue to have no access to either of the external SD cards, which for me is a show-stopper. I'll have to stick with the 0522 Unofficial for a while, at least it's fully functional for me..
Click to expand...
Click to collapse
I've got nothing better to do than blow up my tab every few days so I'll keep posting up results when I do, lol.
The latest nightly has a force close on System UI. I even wiped EVERYTHING and did a clean install... Same thing. Going back one night, and things should be just fine!
Micro SD card isn't working yet, but this is just a nightly... I'm not worried about it.
HDMI out is working, so that's awesome!
Thanks for testing the unofficial editions. I think it will be better soon!
I m using the app "rotate" to make the table force rotate. It will be useful in the unofficial roms.
Sent from my Galaxy Nexus using xda premium
07032013 build OK. July 4th and after give the FC's.
Sent from my EPAD using Tapatalk HD
mm284781423 said:
Thanks for testing the unofficial editions. I think it will be better soon!
I m using the app "rotate" to make the table force rotate. It will be useful in the unofficial roms.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
post a link for this app?Thanks
2013/07/08 build still has UI crashes.
Is there anyone from the CM team watching this thread? If there is I will gladly post a logcat when I get the chance.
nexwave-mat said:
Is there anyone from the CM team watching this thread? If there is I will gladly post a logcat when I get the chance.
Click to expand...
Click to collapse
Post, and I'll see what I can do...
Auto-rotate and the dock stuff is already in the review process.
who have tested the 08\07 nighly? FC?
Me. With Clean install
Sent from my Galaxy Nexus using xda app-developers app
atoyu said:
Me. With Clean install
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
And ? Any UI crash issues ? sd-card ? rotate ?
demercie said:
And ? Any UI crash issues ? sd-card ? rotate ?
Click to expand...
Click to collapse
@atoyu
so what?
The SystemUI was on my nexus 4 too... and I experienced it on this so here is the commits they shared in the nexus4 thread to fix it... if it helps or if anyone reads these...
BTW I have no idea if these really are the culprit but thats what they gave us in the n4 thread
http://review.cyanogenmod.org/#/c/45076/
and possibly
http://review.cyanogenmod.org/#/c/45102/
although not sure about that one...
Sent from my EPAD using xda app-developers app
M8 has L few days, cm12 also ready... So many people are wating L for Dna.
Who dev can port plzzz!!
Thk so much
It's in the works. Worked through camera fails and trying to fix GPS fails at the moment. CM is working on dlx too. I got grouper on team eos right now, and a few other guys got devices booting. Dlx is what I'm working on now.
danjull said:
It's in the works. Worked through camera fails and trying to fix GPS fails at the moment. CM is working on dlx too. I got grouper on team eos right now, and a few other guys got devices booting. Dlx is what I'm working on now.
Click to expand...
Click to collapse
watiinggg...
is it comming soon...??
loveuhp said:
watiinggg...
is it comming soon...??
Click to expand...
Click to collapse
OMG please don't push the man.........there's just a few keeping the DNA alive and we don't want to p!ss anyone off by implying they hurry..........
danjull said:
It's in the works. Worked through camera fails and trying to fix GPS fails at the moment. CM is working on dlx too. I got grouper on team eos right now, and a few other guys got devices booting. Dlx is what I'm working on now.
Click to expand...
Click to collapse
How did you get past the camera fails? I tried to build cm12 for the DNA and it kept failing with errors related to the camera.
yukongt300ex said:
How did you get past the camera fails? I tried to build cm12 for the DNA and it kept failing with errors related to the camera.
Click to expand...
Click to collapse
What errors? Don't have my source up on github yet, but this is pretty much it.
https://github.com/CyanogenMod/andr...mmit/970cdb1fcaa76ac8e741cb5a24846b2c6f7009eb
If you're building cm, you'd want to run a fresh sync. Lots of commits pushed today that's dlx related.
LuckyPuppy said:
OMG please don't push the man.........there's just a few keeping the DNA alive and we don't want to p!ss anyone off by implying they hurry..........
Click to expand...
Click to collapse
One simple rule that has been said countless times around the forum: NEVER ASK FOR AN ETA. Any & all devs will release when it is deemed fully functional. I personally still appreciate all the devs who are still on the DLX, being the fact that I have 2 of them. I'm in no rush for L, simply because I would like it to be flawless, not rushed along just to get it out. Much appreciated devs, very much so.
Not too bothered by people asking when stuff is coming. I understand the excitement. I'm doing it mainly for myself, so it's coming when it's done. The DNA is still my daily driver, so it and grouper are my priorities. Having people asking about is neither gonna slow it down or speed it up. And it's not gonna tick me off either. I'm gonna keep keeping on either way.
Having that said, I'm just gonna leave this here. It shouldn't be long now. If that's all that's in the way, I already have a fix for that. Just have to start over compiling from scratch. But as you can see I have service, usb is charging, etc.
danjull said:
Not too bothered by people asking when stuff is coming. I understand the excitement. I'm doing it mainly for myself, so it's coming when it's done. The DNA is still my daily driver, so it and grouper are my priorities. Having people asking about is neither gonna slow it down or speed it up. And it's not gonna tick me off either. I'm gonna keep keeping on either way.
Having that said, I'm just gonna leave this here. It shouldn't be long now. If that's all that's in the way, I already have a fix for that. Just have to start over compiling from scratch. But as you can see I have service, usb is charging, etc.
Click to expand...
Click to collapse
You probably just need to do a clean build. The commit which fixes that is the cm commit which removes the hce permission. Once you get it booting, you'll probably find that your in-call audio is borked though.
Looking forward to trying it. Your effort is truly appreciated!
crpalmer said:
You probably just need to do a clean build. The commit which fixes that is the cm commit which removes the hce permission. Once you get it booting, you'll probably find that your in-call audio is borked though.
Click to expand...
Click to collapse
You got it booting on cm?
danjull said:
You got it booting on cm?
Click to expand...
Click to collapse
Yes. It is working pretty well except for the in call audio (selinux permissive though). I can't think of many unmerged changes needed for it, except one needed for the camera (it is in the gerrit comments).
crpalmer said:
Yes. It is working pretty well except for the in call audio (selinux permissive though). I can't think of many unmerged changes needed for it, except one needed for the camera (it is in the gerrit comments).
Click to expand...
Click to collapse
Hmm. It's booting fine for me. In call audio is not working. Screen freezes after about 2 minutes of use though. Selinux permissive here too.
I am getting cm12 to build now but when I try to install it in twrp it is saying "mount: failed to mount /dev/block/mmcblk0p34 at /data: device or resource busy". Any help would be greatly appreciated.
yukongt300ex said:
I am getting cm12 to build now but when I try to install it in twrp it is saying "mount: failed to mount /dev/block/mmcblk0p34 at /data: device or resource busy". Any help would be greatly appreciated.
Click to expand...
Click to collapse
Ignore that. It should flash fine with that error (and the unmount error too).
Is there anything else that needs to be changed to get the DNA to boot? I synced with the cm12 branch about 2 hours ago. After the install it is sitting at the white HTC screen. Does something need to be changed to make it Selinux permissive to get it to boot?
yukongt300ex said:
Is there anything else that needs to be changed to get the DNA to boot? I synced with the cm12 branch about 2 hours ago. After the install it is sitting at the white HTC screen. Does something need to be changed to make it Selinux permissive to get it to boot?
Click to expand...
Click to collapse
Look at the open gerrit commits. There should be one yo make it permissive and maybe one or more other important ones to get it booting.
Got a build up here: http://forum.xda-developers.com/showpost.php?p=57053344&postcount=88
Like it says in that post, bluetooth is messed up for some reason. Haven't ran any logs or anything, but it was working so I assume it'll be up and running shortly. But I've used the rom for a few days, calling, texting, and such. Time frame fix for bluetooth depending on the holidays...
Does anyone have the camera working on Lollipop? I am getting "Camera Error Can't connect to the camera".
yukongt300ex said:
Does anyone have the camera working on Lollipop? I am getting "Camera Error Can't connect to the camera".
Click to expand...
Click to collapse
Yup, working here. What ROM are you using?
[ROM][Unofficial][5.0.2] CyanogenMod 12.0 [1-1-2015]
CyanogenMod 12.0 Unofficial
For the HTC EVO LTE 4G (jewel)
Requirements
You need to be on the new partition layout, have S-OFF, and have Captain_Throwback's TWRP recovery.
Installing
Download the ROM.
Download GAPPS if you want them (make sure they are for the right version of Android).
Boot into recovery.
Wipe system and data.
Install the ROM.
If you wanted GAPPS install them.
Wipe cache and dalvik cache.
Reboot (this will take a while).
Have fun!
Bugs
The notification sound will not change. This may also apply to the ringtone.
As far as I know everything else seems to work. I don't have service on this phone so for data and phone calls and such I cannot say. If anything else doesn't work let me know.
Sources
ROM
Kernel
Downloads
ROM: Next post.
GAPPS​
Official nightly builds are now available here.
Why did you put this under the other CM 12 Unofficial thread? That really should be what you do, or we'll have duplication of discussion. He does have a place in post 2 reserved for partner builds.
ocarinaz64 said:
Why did you put this under the other CM 12 Unofficial thread? That really should be what you do, or we'll have duplication of discussion. He does have a place in post 2 reserved for partner builds.
Click to expand...
Click to collapse
Initially he did exactly that. Then a one of the mods deleted half a dozen posts. Take a look at the mods post in the other thread.
Since the other poster moved on, it's probably best anyway. That way he can update the build dates.
ok, so my brother has a flakey 4g lte. I tried to refresh his phone to stock and he still seems to have some issues.
I would like to throw a custom build on there and I think this would be a great one. He has never been rooted, has taken all the latest OTAs, etc and is S-ON. So... what the best S-OFF to use for the latest firmware one? I am guessing rumrunner? Then from there, TWRP recovery I see is required, but it also says use the new partition layout. Is that the F2FS?
Also, does this rom come with the easy CM updater? Or are they all manual for now?
Thanks.
edufur said:
ok, so my brother has a flakey 4g lte. I tried to refresh his phone to stock and he still seems to have some issues.
I would like to throw a custom build on there and I think this would be a great one. He has never been rooted, has taken all the latest OTAs, etc and is S-ON. So... what the best S-OFF to use for the latest firmware one? I am guessing rumrunner? Then from there, TWRP recovery I see is required, but it also says use the new partition layout. Is that the F2FS?
Also, does this rom come with the easy CM updater? Or are they all manual for now?
Thanks.
Click to expand...
Click to collapse
Is the bootloader unlocked? If not, that's what needs to be done prior to getting S-Off.
Rumrunner should work just fine.
You really need to read and follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2639180
Captain Throwback has done some amazing work and has significantly extended the useful life of our devices. You'll need to use his TWRP too. Nothing else will work.
Hope this helps.
New build.
New build. Sorry it took a while, I was having trouble getting it to build and I just ended up downloading the sources fresh. I'm going to be RMAing my motherboard after Christmas because it currently works with only a single stick of RAM, so it will be a little bit for more builds. I'll be sure to put a new one out before I do though.
Tolipohs said:
New build. Sorry it took a while, I was having trouble getting it to build and I just ended up downloading the sources fresh. I'm going to be RMAing my motherboard after Christmas because it currently works with only a single stick of RAM, so it will be a little bit for more builds. I'll be sure to put a new one out before I do though.
Click to expand...
Click to collapse
Has anyone noticed that focus no longer works in any camera app with the update to 5.0.2? This seems to be present across all 5.0.2 ROM's.
goliath714 said:
Has anyone noticed that focus no longer works in any camera app with the update to 5.0.2? This seems to be present across all 5.0.2 ROM's.
Click to expand...
Click to collapse
I hadn't used the camera yet but checking now it does seem that way.
Tolipohs said:
I hadn't used the camera yet but checking now it does seem that way.
Click to expand...
Click to collapse
I've tried all the current ROM's, AICP, BlissPop, CM, SlimLP, and LiquidSmooth LP and this issue is present in all ROM's so I'm guessing it goes further than just the CM tree.
goliath714 said:
I've tried all the current ROM's, AICP, BlissPop, CM, SlimLP, and LiquidSmooth LP and this issue is present in all ROM's so I'm guessing it goes further than just the CM tree.
Click to expand...
Click to collapse
I think my notification tone is bugged too, is yours?
Tolipohs said:
I think my notification tone is bugged too, is yours?
Click to expand...
Click to collapse
Yes.
goliath714 said:
Yes.
Click to expand...
Click to collapse
Ok, thanks. I'll add these to the op.
Christmas present for you guys.
I'm curious if anyone is using this (or any) cm12 rom on an Activated htc evo 4g lte sprint phone. I ask because I have a couple of these phones that are not activated I give my kids to play with. My wife has this phone also and I'm thinning about installing this on her phone but wanted to know if I should expect any issues with data or GPS. We travel allot so a concern is the ability to quickly transition from 3g to 4g back to 3g. With a "stock based" rom it has no problem but I noticed with cm11 it had issues keeping data
Sent from my HTC One_M8 using Tapatalk 4
knightwolf123 said:
I'm curious if anyone is using this (or any) cm12 rom on an Activated htc evo 4g lte sprint phone. I ask because I have a couple of these phones that are not activated I give my kids to play with. My wife has this phone also and I'm thinning about installing this on her phone but wanted to know if I should expect any issues with data or GPS. We travel allot so a concern is the ability to quickly transition from 3g to 4g back to 3g. With a "stock based" rom it has no problem but I noticed with cm11 it had issues keeping data
Sent from my HTC One_M8 using Tapatalk 4
Click to expand...
Click to collapse
no data transition issues with lp roms. using it now.
Sent from my EVO using XDA Premium 4 mobile app
New build.
Tolipohs said:
New build.
Click to expand...
Click to collapse
You Sir are a CHAMP!
Do you know are the "post-22nd" bugs mentioned in the op still there? I know you're not doing dev on this yourself, just curious if anyone has noted upstream fixes and this thread is pretty quiet.
Wanting to take it for another spin but with small kids and holidays my camera is getting a workout. If not I'll fire it up here in a day or two, check for myself, and report back
Thanks a ton for keeping this going. I'm squeezing every last mile out of this phone as my family is between homes at the moment so I'm squirreling away every dollar I can.
dangle79 said:
You Sir are a CHAMP!
Do you know are the "post-22nd" bugs mentioned in the op still there? I know you're not doing dev on this yourself, just curious if anyone has noted upstream fixes and this thread is pretty quiet.
Wanting to take it for another spin but with small kids and holidays my camera is getting a workout. If not I'll fire it up here in a day or two, check for myself, and report back
Thanks a ton for keeping this going. I'm squeezing every last mile out of this phone as my family is between homes at the moment so I'm squirreling away every dollar I can.
Click to expand...
Click to collapse
Still doing it on my phone. I'll probably do a new build when I go to bed.
EDIT: Now I'm not an expert at this but this looks like it should fix it, so I guess in the morning I'll find out, I'll be sure to change the OP if it does.
Q&A for [ROM][5.0.2] OMNI - i777 [UNOFFICIAL] beta
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][5.0.2] OMNI - i777 [UNOFFICIAL] beta. 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!
cyril279 said:
@coolerboyj, I just tried it. I turned off the wifi, then rebooted, and the device booted into android as expected.
I have not tried shift with Omni 5.0, but it should work well.
Click to expand...
Click to collapse
This rom does have random reboots when opening games, like Clash of Clans (works like 20% of the time)
I was wondering if there was a fix.
Thanks in advance
coolerboyj said:
This rom does have random reboots when opening games, like Clash of Clans (works like 20% of the time)[...]
Click to expand...
Click to collapse
MONSTERELLEVEN said:
i have had some random reboots and the call bug as you mentioned but other than that all is good.[...]
Click to expand...
Click to collapse
Regarding the random reboots, are you using the stock kernel?
cyril279 said:
Regarding the random reboots, are you using the stock kernel?
Click to expand...
Click to collapse
yes am using the stock kernel, didnt mess with anything at all
Good to know. I haven't experienced any of the random reboots yet, but I am not a heavy-user beyond a few utility apps, text, email, and calling.
I do know that there seem to be a considerable number of apps that work fine on 4.4 that exhibit undesirable behavior on 5.0. It isn't obvious whether the issues are app compatibility, or that our device tree isn't yet up to par, or that android 5 isn't yet up to par (or even all of the above).
MONSTERELLEVEN said:
yes am using the stock kernel, didnt mess with anything at all
Click to expand...
Click to collapse
cyril279 said:
Good to know. I haven't experienced any of the random reboots yet, but I am not a heavy-user beyond a few utility apps, text, email, and calling.
I do know that there seem to be a considerable number of apps that work fine on 4.4 that exhibit undesirable behavior on 5.0. It isn't obvious whether the issues are app compatibility, or that our device tree isn't yet up to par, or that android 5 isn't yet up to par (or even all of the above).
Click to expand...
Click to collapse
am not a heavy user myself but i think you are right about andoid 5 isnt ready yet, actually it reminds me exactly of mircrosoft and the transformation from windows 7 to windows 8
cyril279 said:
Regarding the random reboots, are you using the stock kernel?
Click to expand...
Click to collapse
Yes, the one thats provided with the ROM.
This ROM only claims to have the video recording bug.
I haven't tested it, but thought id give you the link.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-12-t2955551
DELETE
coolerboyj said:
This ROM only claims to have the video recording bug.
I haven't tested it, but thought id give you the link.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-12-t2955551
Click to expand...
Click to collapse
I think i9100 lollipop rom by @Lysergic Acid also doesn't have "No Sound issue on outgoing calls"
Can I flash omni using CWM recovery. I'm using shift kernel and cyanidel from @rogersb11.
pg1980 said:
Can I flash omni using CWM recovery. I'm using shift kernel and cyanidel from @rogersb11.
Click to expand...
Click to collapse
If you are using my kernel and the philz recovery that comes with it you can flash anything lol
My phone burns and reboot when I try to open some apps.
I need some help for this, I'm using OmniRom 5.0.2 lollipop unofficial and when I use the music player of the rom, my phone gets so hot and battery drains to fast, also reboot when try to use other apps from the play store like, youtube, etc... everything else works fine. I want to know if you are going to fix the other bugs like the outgoing calls, etc..??
BTW, thank you so much for your effort on this rom, i really like OmniRom and I hope you can make it better and keep GS2 alive
I have found that there are specific apps that cause the device to immediately reboot. I believe this to be mainly a result of the current memory issues regarding this device and Lollipop.
I haven't experienced any heating issues beyond the initial firmware settling (scanning the device) .
I hope to be able to find a solution to all bugs, but I cannot promise that it will happen.
JCPALACIOSG said:
I need some help for this, I'm using OmniRom 5.0.2 lollipop unofficial and when I use the music player of the rom, my phone gets so hot and battery drains to fast, also reboot when try to use other apps from the play store like, youtube, etc... everything else works fine. I want to know if you are going to fix the other bugs like the outgoing calls, etc..??
BTW, thank you so much for your effort on this rom, i really like OmniRom and I hope you can make it better and keep GS2 alive
Click to expand...
Click to collapse
@rogersb11,
I don't see anything onvious here at all. The call goes through, so it isn't even obvious which errors are relevant if any. Maybe you've already looked through one of these:
http://pastebin.com/z039Bktb
-Cyril
cyril279 said:
@rogersb11,
I don't see anything onvious here at all. The call goes through, so it isn't even obvious which errors are relevant if any. Maybe you've already looked through one of these:
http://pastebin.com/z039Bktb
-Cyril
Click to expand...
Click to collapse
Just seeing this, sorry. I'll pull it now, this call bug log?
Edit: I see that it is, hard to scan it well on my phone, I'll look once I'm at my computer. I updated audio stuff before my last build but no luck. I think using a prebuilt hwcomposer from kk would solve many many issues with video etc. That's what we did for n2 and we don't have official cm12 either. I need to pull a kk zip to get the hwcomposer and see how that works. Also I may need to build an i777 almost stock kernel with my n2 source because only my kernel on n2 will allow working everything hardware. My i777 kernel is based on cm but my n2 is Samsung kernel source 3.0.31 that has been routinely merged with aosp. Quick glance looks like audio isn't routing properly but I could be wrong. It's such a strange bug since it works just fine after flipping on and off. Again sorry for the delay, I seriously only get about 15% of the notifications I should
Yeah, this is the call log, and without something flagrantly crashing (and leaving a better calling card) I have nothing specific to look into.
No worries about the notification, I've been working on slim with warrior1208. ... Although until slim is back online, that project is almost stalled.
We'll have a proper daily driver if we can get this. I can't help but wonder if some of the "under the hood fixes" of 5.1 may help. Prolly just wishful thinking.
rogersb11 said:
Just seeing this, sorry. I'll pull it now, this call bug log?
Edit: [...] Quick glance looks like audio isn't routing properly but I could be wrong. It's such a strange bug since it works just fine after flipping on and off. Again sorry for the delay, I seriously only get about 15% of the notifications I should
Click to expand...
Click to collapse
cyril279 said:
Yeah, this is the call log, and without something flagrantly crashing (and leaving a better calling card) I have nothing specific to look into.
No worries about the notification, I've been working on slim with warrior1208. ... Although until slim is back online, that project is almost stalled.
We'll have a proper daily driver if we can get this. I can't help but wonder if some of the "under the hood fixes" of 5.1 may help. Prolly just wishful thinking.
Click to expand...
Click to collapse
Right now I currently despise 5.1 LOL. Not that it's bad but I have to start over if I want it. Hey, I remember you cooking your mobo awhile back, used to do it all the time but can't remember. What temperature and for how long did you do it? I wanna give it a go on MTT jtagged Xbox. It finally fried so figure might as well give it a shot, heat gun isn't working and my reball machine crapped out least year so I sold it to someone willing to fix it at the time
rogersb11 said:
Right now I currently despise 5.1 LOL. Not that it's bad but I have to start over if I want it. Hey, I remember you cooking your mobo awhile back, used to do it all the time but can't remember. What temperature and for how long did you do it? I wanna give it a go on MTT jtagged Xbox. It finally fried so figure might as well give it a shot, heat gun isn't working and my reball machine crapped out least year so I sold it to someone willing to fix it at the time
Click to expand...
Click to collapse
I used this procedure once to cook the mobo and it worked out for me. I was skeptical but it works:
http://forum.notebookreview.com/thr...-bake-your-gpu-for-fun-and-for-profit.437683/
Saved in the bookmarks
rogersb11 said:
Right now I currently despise 5.1 LOL. Not that it's bad but I have to start over if I want it. Hey, I remember you cooking your mobo awhile back, used to do it all the time but can't remember. What temperature and for how long did you do it? I wanna give it a go on MTT jtagged Xbox. It finally fried so figure might as well give it a shot, heat gun isn't working and my reball machine crapped out least year so I sold it to someone willing to fix it at the time
Click to expand...
Click to collapse
385 for ten minutes brought me success. For two different devices.
I noticed that 5.1 seemed to temporarily push asimovi's progress backward a bit, which is a part of why I haven't published a 5.1 Omni. I lost internal storage again, and haven't found the culprit. I keep forgetting to look into system_vold.
5.0 should have been a test release.
Hey guys. Does anybody know what bugs/missing functionality we currently have with the LineageOS 14.1 nightlies? https://download.lineageos.org/h830
I'm not a huge fan of LG's stock ROM, but I would like full functionality of my phone if I switch to a custom ROM. Thanks!
kaden93 said:
Hey guys. Does anybody know what bugs/missing functionality we currently have with the LineageOS 14.1 nightlies? https://download.lineageos.org/h830
I'm not a huge fan of LG's stock ROM, but I would like full functionality of my phone if I switch to a custom ROM. Thanks!
Click to expand...
Click to collapse
You can never get full functionality of LG Stock ROM on any custom ROMs.
Even though I have not flashed LOS, I can tell you few things that may not work.
1. Wide Camera
2. IR Blaster
3. Most Probably any friends modules if you own them.
I'm interested in knowing too before I try it. As long it's stable with all cameras working, I'd be fine.
rjmohit said:
I'm interested in knowing too before I try it. As long it's stable with all cameras working, I'd be fine.
Click to expand...
Click to collapse
I'm pretty sure the 306 pages of the LOS thread will have most of those answers ...
Nimueh said:
I'm pretty sure the 306 pages of the LOS thread will have most of those answers ...
Click to expand...
Click to collapse
How do you expect anyone to read through 300+ pages where things change all the time?
I asked the same question on Reddit and people were more helpful:
https://www.reddit.com/r/LineageOS/comments/81qtq6/new_g5_h830_user/
https://www.reddit.com/r/lgg5/comments/81qvyo/new_g5_h830_user/
rjmohit said:
How do you expect anyone to read through 300+ pages where things change all the time?
I asked the same question on Reddit and people were more helpful:
https://www.reddit.com/r/LineageOS/comments/81qtq6/new_g5_h830_user/
https://www.reddit.com/r/lgg5/comments/81qvyo/new_g5_h830_user/
Click to expand...
Click to collapse
Good luck on Reddit, the 1st reply in the 1st link is already total and utter bullsh*t
Given the choice of being spoon-fed crap on Reddit and using the search here or simply checking the last few pages ... I'd go for XDA, but that's of course up to you.
kaden93 said:
Hey guys. Does anybody know what bugs/missing functionality we currently have with the LineageOS 14.1 nightlies? https://download.lineageos.org/h830
I'm not a huge fan of LG's stock ROM, but I would like full functionality of my phone if I switch to a custom ROM. Thanks!
Click to expand...
Click to collapse
Well, I've been on los for a while now..
-As far as I know NFC is not working (on not using it so no idea, but it seems to drain the battery an not work properly)
-BT works for eg headphones but not for headsets
Charging is still an issue. It is faster now but still not even close to fast charging. An on a 3rd party charter or is ridiculously slow
-the wide angle camera is working but you have to toggle between the cameras to get to it. The auto focus might be a problem, but it is mostly solved I think.
-playing music is sometimes a drag, and can be laggy
-FM radio is non existing, not supported, will probably never be...
Other issues have been solved, other pop up, but since there are weekly updates, that's what it is.
-be careful, root has to be installed separately and if you don't do so, immediately after installing the ROM, you will most likely end up in the famous Twrp bootloop..
Before installing it I'd read at least the last 20 pages in the forum, these should give you an idea... Or go to the fulmics ROM. It is stock based so everything should be working. To my knowledge all the LOS based ROMs share the same issues.