Now Presenting AOKP KitKat for the Quincyatt ported from the Hercules
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device: Quincyatt (SGH-I717)
>> Installation is simple:
If coming from another ROM or another major AOKP version, wipe data in recovery
Make sure you're using the latest CWM or TWRP 2.6.1.0 (Not TWRP 2.6.3.0)
Quincyatt guys and Gals can use TWRP 2.7.0.0+
Flash ROM
Flash Google Apps (GAPPS)
Reboot
>> Check merged commits on AOKP's Gerrit
_____Quincyatt Builds_____
AOKP
Special Thanks
AOKP
CM
Rookie Thread
Everyone that enjoys this Rom
AOKP Gerrit
AOKP on Github
Source on AOKP.co
We greatly appreciate your contribution in the form of code, or PayPal donations.
>> Donation options on
AOKP.co
Enjoy!
***NOTE***
for netflix work around due to distorted videos use this thanks to @mariasnowhite for pointing it out.
If your SD card isn't mounting like how it should do this edit all thanks to @vinman12
Source build of AOKP can be found in the "source build" folder, other roms that are not in that folder are ports done by me
***My Personal Thanks***
@Kiltnar for allowing me to port his AOKP build.
@patch_Adams for allowing me to use his Liquid Smooth as a base as well as kernel.
XDAevDB Information
AOKP KitKat, ROM for the AT&T Galaxy Note
Contributors
Kiltnar, AOKP_ROM
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: AOKP
Version Information
Status: Beta
Created 2014-03-20
Last Updated 2014-12-09
before i forget no need for flashing screen flicker patch as its already included in the build.prop.
I installed it, and so far no problems on my phone, apps working fine ,no problems with video recording or viewing them from the gallery, hangout, facebook messenger working fine, also whatsapp. still installing apps , but GOOD work on this one!
snipekill said:
I installed it, and so far no problems on my phone, apps working fine ,no problems with video recording or viewing them from the gallery, hangout, facebook messenger working fine, also whatsapp. still installing apps , but GOOD work on this one!
Click to expand...
Click to collapse
I'm glad to hear some positive feed back about this port, was a bit worried due to the fact I'm new to this device. still trying to learn the ins and outs but things are coming along nicely though.
Sent from my Half Baked Vibrant
Well Good Job!:good: So far no screen flicks and everything working smooth. The only thing i am watching for now is the charging cause i have it plug in for almost 2 hours and still on 34% , i will keep watching it cause i am not using any application at the moment to seehow long it take to complete charge and how much will take to drain the same ,but NO COMPLAIN about it. Keep It going.
flashed this rom on my Tmobile note with Pollution patch. everything work exept no data, any way to fix it? please
le2010 said:
flashed this rom on my Tmobile note with Pollution patch. everything work exept no data, any way to fix it? please
Click to expand...
Click to collapse
try flashing a different modem/radio. I had to swap out ril related files from base to port to get data working. do you have any APN settings? if so try to set it to the first apn which is metropcs I believe.
Sent from my Half Baked Vibrant
le2010 said:
flashed this rom on my Tmobile note with Pollution patch. everything work exept no data, any way to fix it? please
Click to expand...
Click to collapse
Isn't this for AT&T? I think Tmo users just enable AWS with WCDMA 1700
@dzee206 - congrats on this ROM! :highfive:
AGLtech said:
Isn't this for AT&T? I think Tmo users just enable AWS with WCDMA 1700
Click to expand...
Click to collapse
yes its for att but originally for tmobile. that wasn't the case for me and I'm with T-Mobile if it matters. I didn't do anything special to get data thus the reason I said try a different radio. just to throw it out there I'm on blazes ICS modem I believe at least I think I am since it says unknown baseband in device info and just happens to be the only one I have stored on my internal.
Sent from my Half Baked Vibrant
Rock solid
So far it's been rock solid. Using as my daily driver. Thanks. :good:
CGRAHAM10 said:
So far it's been rock solid. Using as my daily driver. Thanks. :good:
Click to expand...
Click to collapse
thanks mate. glad things are running smooth for you, I may bring another port to the table but that's if only I can figure out a solution to a problem I'm having with it.
Sent from my Half Baked Vibrant
I've been using it for about a week now as my daily driver. So far, so good. Great job!
snipekill said:
I installed it, and so far no problems on my phone, apps working fine ,no problems with video recording or viewing them from the gallery, hangout, facebook messenger working fine, also whatsapp. still installing apps , but GOOD work on this one!
Click to expand...
Click to collapse
Does this work with the video call of hangout ？
fieldside said:
Does this work with the video call of hangout ？
Click to expand...
Click to collapse
honestly I wouldn't know as I don't use hangouts let alone video calls, personally I hate it and resorted to putting a piece of electrical tape over my FFC. can you test it if you're already on this port? I'm not at home and don't have my note on me atm.
Sent from my Half Baked Vibrant
How is Bluetooth with this ROM? I know that some other ROMs have Bluetooth dropout/crashout issue, and that the BlownFuze AOKP ROM (which I've been using for quite some time) has no issues whatsoever. I can deal with the other issues (camera, screen flicker) but really need confidence in the Bluetooth performance before I can consider switching.
Madmanguruman said:
How is Bluetooth with this ROM? I know that some other ROMs have Bluetooth dropout/crashout issue, and that the BlownFuze AOKP ROM (which I've been using for quite some time) has no issues whatsoever. I can deal with the other issues (camera, screen flicker) but really need confidence in the Bluetooth performance before I can consider switching.
Click to expand...
Click to collapse
perfectly understandable as for your question I don't use BT but I did manage to pair my note with my galaxy for a good 15-20 minutes so I'd say it works. no screen flickering as I included the patch into the build.prop, performance wise I can't complain haven't had any major issues while I was running it. actually you caught me at the right time was just about to give the 8/12 build of PAC a try. almost forgot to mention camera seems to be good as well. let me know if you run into any issues with any thing.
Sent from my Half Baked Vibrant
dzee206 said:
perfectly understandable as for your question I don't use BT but I did manage to pair my note with my galaxy for a good 15-20 minutes so I'd say it works. no screen flickering as I included the patch into the build.prop, performance wise I can't complain haven't had any major issues while I was running it. actually you caught me at the right time was just about to give the 8/12 build of PAC a try. almost forgot to mention camera seems to be good as well. let me know if you run into any issues with any thing.
Sent from my Half Baked Vibrant
Click to expand...
Click to collapse
Thanks for the update. I find that BT can sometimes work for a few hours, sometimes a day or two before it gives out (on a bad ROM) - when it flakes out you have no choice but to reboot to get it back which is a pain when you're driving.
Madmanguruman said:
Thanks for the update. I find that BT can sometimes work for a few hours, sometimes a day or two before it gives out (on a bad ROM) - when it flakes out you have no choice but to reboot to get it back which is a pain when you're driving.
Click to expand...
Click to collapse
I use this ROM with 2 different Samsung BT headsets. I will occasionally receive a message that the BT service has stopped/died. Fortunately, BT continues to work after I toggle it off and back on. I haven't had to reboot yet to get it to work. The previous ROM I used before this one would regularly kill BT and require a reboot for it to begin working again.
Tried this out, Bluetooth seems to have the same issues as ever other non blown fuse ROM, namely needs reboot every third or forth pairing and often can't cycle BT on then off correctly.
Back to bf aokp .
Sent from my SGH-I717 using XDA Free mobile app
Related
Just heard that there is a maintenance ROM release for Sprint devices coming on Friday, 11/30. This is NOT the Rev A and GPS release. Its supposed to have some bluetooth fixes, among other things. It should be posted on the HTC website on Friday.
And you heard this from where???
so what else is NEW?
This is the promised ROM they refer to on this page.
http://www.america.htc.com/support/mogul/software-downloads.html
in this paragraph
"Sprint and HTC regret any inconvenience customers have recently experienced with the Mogul. HTC is working on a new version of the software ROM for the Mogul which incorporates enhancements for Bluetooth performance and corrects issues that were unintentionally created by ROM version 2.16.651.0 (posted on HTC’s website on October 24). Both Sprint and HTC have begun testing the new software and are targeting to make it available for download by the end of November. Once fully tested the download will be made available on this webpage. Please bookmark this page for easy reference."
Common knowledge at this point.
austinbrady said:
This is the promised ROM they refer to on this page.
http://www.america.htc.com/support/mogul/software-downloads.html
in this paragraph
"Sprint and HTC regret any inconvenience customers have recently experienced with the Mogul. HTC is working on a new version of the software ROM for the Mogul which incorporates enhancements for Bluetooth performance and corrects issues that were unintentionally created by ROM version 2.16.651.0 (posted on HTC’s website on October 24). Both Sprint and HTC have begun testing the new software and are targeting to make it available for download by the end of November. Once fully tested the download will be made available on this webpage. Please bookmark this page for easy reference."
Common knowledge at this point.
Click to expand...
Click to collapse
The new ROM has been posted.
http://download.america.htc.com/RUU_TITAN_SPRINT_WWE_2.17.651.0_RS_TITAN_SPCS_1.47.01_Ship.exe
??? How did you find this link. Its not posted any where on their site
So, who's going to be the guinea pig?
I guess me. I just got this phone last week so i dont have much to loose. In progress right now.
johnnychimpo said:
??? How did you find this link. Its not posted any where on their site
Click to expand...
Click to collapse
A lot of people on ppcgeeks are having the same problem. They can't see the page but the download is working. It is available.
Well, seems to be working just fine. The damn alarm clock works now when you have the charger hooked up!
I dont have a bluetooth headset thats charged right now to confirm if that issues is resolve though.
Nice new splash screen on start...
johnnychimpo said:
??? How did you find this link. Its not posted any where on their site
Click to expand...
Click to collapse
They didn't update the screen shot, but if you go down to the down link it shows the new version.
Any word on the roaming freezing problems?
The new ROM is up a day early at:
http://www.america.htc.com/support/mogul/software-downloads.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cdoggwsu said:
Any word on the roaming freezing problems?
Click to expand...
Click to collapse
I installed 2.17 last night. I previously had the roaming lockup problem with 2.16 set to 'Automatic' just stepping into the elevator at my office. This morning with 2.17 and roaming setup to 'Automatic' no lockup riding the elevator.
I also experienced the Dpad issue on 2.16 with Bluetooth enabled. With 2.17 and Bluetooth enabled the Dpad is functioning just fine. I also bought a Plantronics 520 headset this week that is BT 2.0 and it is working just fine.
Regards,
Tom
tpbklake said:
I installed 2.17 last night. I previously had the roaming lockup problem with 2.16 set to 'Automatic' just stepping into the elevator at my office. This morning with 2.17 and roaming setup to 'Automatic' no lockup riding the elevator.
I also experienced the Dpad issue on 2.16 with Bluetooth enabled. With 2.17 and Bluetooth enabled the Dpad is functioning just fine. I also bought a Plantronics 520 headset this week that is BT 2.0 and it is working just fine.
Regards,
Tom
Click to expand...
Click to collapse
Thanks for the update, Tom! I too got a little impatient last night and installed the new rom. I've yet to run into the same roaming problems inherent in the 2.16 release and everything else seems to be running well. I suppose only time will tell at this point.
This is great news! I downloaded the ROM this morning, but I have been waiting until the weekend to install it to see what the early adopters had to say. Great to hear that it seems to be working better.
Doug
tpbklake said:
I also experienced the Dpad issue on 2.16 with Bluetooth enabled. With 2.17 and Bluetooth enabled the Dpad is functioning just fine. I also bought a Plantronics 520 headset this week that is BT 2.0 and it is working just fine.
Regards,
Tom
Click to expand...
Click to collapse
Observations:
-DPad working when BT enabled.
-BT working with a Motorola H500 headset. Will also test a Plantronics 510, Motorola S9, and H9 in the next couple of days.
-The ROM is more responsive (paginates more quickly) and transitions from portrait to landscape more faster as well.
Here's a question. Remember back when the Mogul came out, to make the battery last you had to hack 4 reg keys? Have you guys had to do that with 2.17 at all?
ldubin said:
Here's a question. Remember back when the Mogul came out, to make the battery last you had to hack 4 reg keys? Have you guys had to do that with 2.17 at all?
Click to expand...
Click to collapse
I never did the power hacks for the last rom and I can get 2-2.5 days with normal use, although the phone goes on the charger every night regardless. I've only been using this rom since about 11:30 last night but it seems to be the same as before.
I don't know if it's just me but it seems that I have had less signal bars since upgrading to the 2.17 rom. I am convinced, however, that the Mogul is just not very good at displaying it's bars. Whether I have "full signal" or only 1 bar my calls are always clear and I have yet to drop one, so even if it appears as less I haven't had any issues.
Lucky...i only got 12-14 hours normal use, email check every 10 min, no bluetooth, but I'm ok with that. I'll wait another day or so but this ROM looks promising
does this new rom erase the memory on ythe phone so that ill have to reinstall everything? i have a nice setup and an incrremental upgrade wouldnt be worth it
Hi so I am s-off, unlocked and rooted.. I updated to the latest wwe firmware and since then, my google apps like chrome, maps and Google search will not work when connected to data/LTE from time to time..it will not load the search even though I am connected to LTE.. I have to use another browser just to search on google. Anyone else have similar issues or fixed?
Sent from my HTC One_M8 using XDA Free mobile app
You can try flashing the Dev Ed (3.28.1540) firmware. Although Wonders_Never_Cease seems to be saying the radio is same as Euro firmware.
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365/page50
On the 2.x firmware, folks had various issues (including LTE issues or no service whatsoever) using the Euro radio on US networks. However, yours is the first report I've seen of issues with the 3.28.401 firmware on US networks (assuming that is the case).
redpoint73 said:
You can try flashing the Dev Ed (3.28.1540) firmware. Although Wonders_Never_Cease seems to be saying the radio is same as Euro firmware.
http://forum.xda-developers.com/att...2-22-1540-3-debloated-sense-6-t2837365/page50
On the 2.x firmware, folks had various issues (including LTE issues or no service whatsoever) using the Euro radio on US networks. However, yours is the first report I've seen of issues with the 3.28.401 firmware on US networks (assuming that is the case).
Click to expand...
Click to collapse
OK I will try that. And yes I'm on us AT&T network. Very strange that no one else is having this issue
Sent from my HTC One_M8 using XDA Free mobile app
I'm having the same problem but it doesn't make sense. I flashed the firmware yesterday and I'm only getting this connection problem today. So far I've dirty flashed, clean flashed, flashed a new radio. My next attempt is to reflash a different firmware. It doesn't help that the WiFi at work is down so it's making me all types of cranky, if all else fails the phones meeting the wall.
Actually this is probably a Google issue. Now YouTube, Gmail, Maps, Keep and Play Music all work properly for me. The only thing still borked is Play Store
Update: Just clear data on Play Store, everything should be working now. At least it is for me. @sameer1807
WTFunk said:
Actually this is probably a Google issue. Now YouTube, Gmail, Maps, Keep and Play Music all work properly for me. The only thing still borked is Play Store
Update: Just clear data on Play Store, everything should be working now. At least it is for me. @sameer1807
Click to expand...
Click to collapse
Interesting. The fact it was only Google services that were affected did have me suspicious. So the firmware may just be coincidence and a red herring.
redpoint73 said:
Interesting. The fact it was only Google services that were affected did have me suspicious. So the firmware may just be coincidence and a red herring.
Click to expand...
Click to collapse
I tried clearing google play store, services framework, google search and chrome data..now I'll just need to observe
Sent from my HTC One_M8 using XDA Free mobile app
sameer1807 said:
I tried clearing google play store, services framework, google search and chrome data..now I'll just need to observe
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
It's actually still going up and down for me. Play Store is choosing when it wants to load. The rest of my Google apps are fine now.
WTFunk said:
It's actually still going up and down for me. Play Store is choosing when it wants to load. The rest of my Google apps are fine now.
Click to expand...
Click to collapse
seem to have the same problem even after clearing the data. i will try flashing the at&t fw like someone above recommended. hope that fixes the issue.
Compared radio version [email protected],but how its use by network on euro build props is another story, the euro builds on att network seem to not work as well.
redpoint73 said:
You can try flashing the Dev Ed (3.28.1540) firmware. Although Wonders_Never_Cease seems to be saying the radio is same as Euro firmware.
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365/page50
On the 2.x firmware, folks had various issues (including LTE issues or no service whatsoever) using the Euro radio on US networks. However, yours is the first report I've seen of issues with the 3.28.401 firmware on US networks (assuming that is the case).
Click to expand...
Click to collapse
Ok so even after flashing the at&t fw for 4.4.4, no luck. looks like i have to revert back to 4.4.3 and the 2.22 fw. do not know what the source of this problem is.
sameer1807 said:
looks like i have to revert back to 4.4.3 and the 2.22 fw. .
Click to expand...
Click to collapse
I'd be interested to see if that helps, or eliminates FW as the issue.
LTE issues makes me think its a radio issue. But the fact its just Google services makes me think otherwise. So its an interesting case.
redpoint73 said:
I'd be interested to see if that helps, or eliminates FW as the issue.
LTE issues makes me think its a radio issue. But the fact its just Google services makes me think otherwise. So its an interesting case.
Click to expand...
Click to collapse
Yes I put the 2.22 fw back and installed a 4.4.3 ROM and problem solved.. Guess I have to wait until att releases an official release. Good thing not much has changed in 4.4.4
Sent from my HTC One_M8 using XDA Free mobile app
This guy is having the same issue on 4.4.3 and seems to be running stock: http://forum.xda-developers.com/showpost.php?p=56187474&postcount=3
So I'm still thinking maybe its just a network or Google issue?
This thread seems more active than the one that I had originally posted on, so I'll jump on here. I came from an iPhone 5 because I had really wanted out of the iOS ecosystem and after having a Nexus tablet for a bit I was ready to make the jump. I picked up a used DE 32GB m8. The previous user had said he only used it for a week before deciding he liked his Note 3 more, and was also using it on AT&T. When I got the phone it was running KK 4.4.3 but I'm not sure of the firmware/baseband versions, I just didn't take notice, I'm sorry. At 1st the phone seemed to connect to LTE just fine...I entered my Google account on it and it set it up pretty much as a carbon copy of my Nexus 7 tablet. During this time a ton of apps downloaded, but not all the ones I wanted on a phone vs. a tablet so I definitely went to the Play Store and grabbed a few. This was when I was still up in the Waterbury, CT area where I had picked up the phone. It wasn't until about a week later that I noticed connectivity issues while showing LTE signal. I at 1st thought it applied to all services but it turned out it was just the Google services (minus play music, for whatever reason) I called AT&T who verified my LTE connectivity and downloaded Ookla Speedtest to verify for myself. My downstream averages over 50mb/s and upstream about 20mb/s. After trying all the trouble shooting steps like clearing all caches, reverting gapps back to stock, etc. I performed a factory reset. This STILL did not solve my connection issues. Also I have verified during this time I can connect fine by selecting the H+ network. When OTA 4.4.4 was released I thought that may fix the issue. It did not seem to change anything regarding LTE connectivity. BTW on both 4.4.3 and 4.4.4 I have been using ART runtime. I then decided to unlock the boot loader and root the phone, as I had done for my Nexus. I did and went in through ES file explorer to delete the hosts.txt file in system/etc as that had been mentioned as a way to restore Play Store connectivity. All last night and this morning my LTE was working fine, until I got to work. Although it was showing LTE service there once again I got timeout errors on the Play store and Google.com and search were not functional until I switched LTE off. When the H+ connection was restored, I could connect again. I called Google tech support regarding this issue and they advised me to call AT&T or HTC as it was "not their issue". I'm hoping that one of us can figure this out. I am considering going S-off and flashing radios when I have the time to experiment. I may eventually go to a custom ROM as well but I wanted to hold out for Lollipop.
To the above post..yes seems like your issue is similar to mine except you experienced it without flashing the 4.4.4 firmware. Anyway, the only fix I found after being on 4.4.4 and having weird google issues on LTE, I flashed a 4.4.3 fw and flashed recovery/flashed SuperSU/installed ROM and everything is back to how it was before I decided to flash the updated fw. But to do all of these things, like u said, you must be s-off and boot loader unlocked.
Sent from my HTC One_M8 using XDA Free mobile app
sameer1807 said:
To the above post..yes seems like your issue is similar to mine except you experienced it without flashing the 4.4.4 firmware. Anyway, the only fix I found after being on 4.4.4 and having weird google issues on LTE, I flashed a 4.4.3 fw and flashed recovery/flashed SuperSU/installed ROM and everything is back to how it was before I decided to flash the updated fw. But to do all of these things, like u said, you must be s-off and boot loader unlocked.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Wow ok I'm having the exact same problem as you guys...but I heard it's not good running a 4.4.4 with a 4.4.3 fw...is everything working well since u have? I thought maybe it was a radio issue myself...
Sent from my HTC One_M8 using XDA Free mobile app
I actually downgraded back to 4.4.3.. Ya if you try running 4.4.3 fw on a 4.4.4 ROM, the device won't boot.
Sent from my HTC One_M8 using XDA Free mobile app
sameer1807 said:
Ya if you try running 4.4.3 fw on a 4.4.4 ROM, the device won't boot.
Click to expand...
Click to collapse
It will probably boot, just take a reeeeally long time to do so (10 minutes or more). And WiFi will probably be broken.
I'm running ROM below and flashed the 3.28.401.6 firmware from the provided link below the image and I'm receiving the best service I've had in places I had nothing at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
the issue isnt so much about getting service as it is about connecting to google svcs like google now/play store/maps/ chrome google search. i agree service has been better but periodically, it cuts off to these svcs. i wish someone would look more into this. IK this seems to be isolated but perfecting this would improve the experience for all users of the M8.
Attached is a picture of what the BSOD looks like. Also attached is a last_kmsg that caught "a" crash. The last_kmsg for this crash appears to not have any info for the crash.
Has anyone found a fix for this?
Alias8818 said:
Attached is a picture of what the BSOD looks like. Also attached is a last_kmsg that caught "a" crash. The last_kmsg for this crash appears to not have any info for the crash.
Has anyone found a fix for this?
Click to expand...
Click to collapse
I'm pretty sure anyone who can help is going to ask about your ROM and any other setup details you think are relevant.
Sent from my LGLS990 using XDA Free mobile app
MikeDroid said:
I'm pretty sure anyone who can help is going to ask about your ROM and any other setup details you think are relevant.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
This has happened on 3 different ROMs. CM12, Blisspop, and Illusion. This has happened on the stock kernel and RIN Kernel 1.65.
Kernel crash, thats what that is it usally happens when the is a kernel based error I recommed staying away from any 4.4.4 roms for now I have had the same problem with thoughs for now the only rom that I don't get that on is this one from clark44:http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197 I recommed you find a rom you like and that works and DO NOT modify/change the kernel. This could also be of you over clocked way to high. So each just reboot and find a rom that dosen't do this and just stick with it without changing kernels.
I believe I will revert back to a Kitkat ROM, sadly, until it's figured out. I haven't played with any kernel settings or OC'd.
Blue Screen
Sadly, I have also been getting these demigod modem crashes with pretty much any 4.44 rom - carbon, liquidsmooth, vanir, my own cm11 build, etc.
Seems to happen every couple days at least - which I can't have with needing alarms, missed calls, etc.
It's a shame as these roms run really well, much better than stock. For the moment I am running barrin rom (stock based) and have no issues - I haven't had any issues with any stock based rom.
Hopefully some of the devs can at least let us know what they are experiencing, and what this means.
mo1991 said:
Sadly, I have also been getting these demigod modem crashes with pretty much any 4.44 rom - carbon, liquidsmooth, vanir, my own cm11 build, etc.
Seems to happen every couple days at least - which I can't have with needing alarms, missed calls, etc.
It's a shame as these roms run really well, much better than stock. For the moment I am running barrin rom (stock based) and have no issues - I haven't had any issues with any stock based rom.
Hopefully some of the devs can at least let us know what they are experiencing, and what this means.
Click to expand...
Click to collapse
Have not experienced this at all but looked at the kmsg in the first post and it indeed seems like a kernel crash based around the soc. It's a modem crash but these phones have different system on chips, not all ls990s are created equal. The same stuff happened with rin when I first built it, green watchdog kernel crash for roughly 3-5% of users. The voltage spectrum was widened to include these other socs and voila, no more green screen for anyone.
I can't promise a fix, I'm overloaded currently - but if I find anything to help you guys, I won't keep it a secret.
News on BSOD
No News here regarding this huh? Too bad as there are a lot of good roms out there and none of them working without BSOD on what appears to be "only some" of the LS990's - sadly mine is one of those.
If any of the Dev's that are more knowledgeable then me want me to do any testing or try to pull some of the files from my phone let me know. Stock based roms work fine. CM11 and AOSP based roms all get the blue screen modem crash - SOC.
mo1991 said:
No News here regarding this huh? Too bad as there are a lot of good roms out there and none of them working without BSOD on what appears to be "only some" of the LS990's - sadly mine is one of those.
If any of the Dev's that are more knowledgeable then me want me to do any testing or try to pull some of the files from my phone let me know. Stock based roms work fine. CM11 and AOSP based roms all get the blue screen modem crash - SOC.
Click to expand...
Click to collapse
I have a T-Mobile sim with an at&t device d850 and I only get the blue screen when using LTE. If I turn off LTE then no problems. Hbu
Sent from my LG-D850 using XDA Free mobile app
Test
4NDROID4LIFE said:
I have a T-Mobile sim with an at&t device d850 and I only get the blue screen when using LTE. If I turn off LTE then no problems. Hbu
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the info. I will give this a test one of these days and see if turning off LTE makes a difference. I don't think I could deal with that as a long term solution as I need fast mobile data, but it would be good to know that the issue is caused by LTE to narrow down potential fixes for the devs.
Fix
Anyone know if the new version of modem helps things?
Or any other fix?
cm12 crash
Just for information, I have also received this modem crash blue screen on the latest cm12 build from 3/1.
Hopefully we will have some idea why this is happening before too long. If anyone has any ideas please let me know. Happy to test.
[ROM][5.0.2][5.1.1] Unofficial Discussion for Cyanogenmod 12 & 12.1 on t0lte (N7105)
Since there didn't seem to be a place for Samsung Galaxy Note 2 LTE (N7105) CM12 users to talk about the latest nightlies here on XDA, I thought I'd take matters into my own hands. If someone from the CM team would like to take over this thread, feel free to shoot me a PM :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 12 and CyanogenMod 12.1 are free, community built distributions of Android 5.0.x (Lollipop) and Android 5. 1 (Lollipop) which greatly extends the capabilities of your phone.
As per usual, a disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Official Nightlies are available for download here: http://www.get.cm/?device=t0lte
Official Gapps are available for download here: http://wiki.cyanogenmod.org/w/Google_Apps
All credits go towards the fantastic people who maintain our device and the CM team :good:
Bootloader
I'm still on 4.1.2 bootloader. Is there any advantage by updating to 4.3 bootloader?
0324 build
Anyone knows if low volume during calls being fixed on recent builds?
Also, how to enable HDMI output to TV ? Is this feature supported yet?
Thank you.
----------------+----------------
On 0324
Both issues above still ain't sorted.......
Also mobile data doesn't work, nor making/receiving calls....
I use teamUB with Agni and almost everything works but memory leak bothers a lot, waiting for 5.1or5.1.1 if there will lol
---------- Post added at 12:34 AM ---------- Previous post was at 12:32 AM ----------
xhizorsz said:
I'm still on 4.1.2 bootloader. Is there any advantage by updating to 4.3 bootloader?
Click to expand...
Click to collapse
I updated from 4.3 bl to a KitKat bootloader but find nothing different, though devs recommended this
I'm on the 4.3 bootloader, no problems. I just got my Note 2 second hand so I didn't have much of a choice in this matter. I think improved modem support is one benefit if it's anything like the Galaxy S4. I have the n7105t, if that makes any difference.
I've noticed a couple of device-specific issues that I will note with a fresh install of the 23rd of March nightly:
1. F2FS doesn't seem supported at this time (did not boot with F2FS on System and Data). Would be nice but not a big deal really.
2. GPS doesn't seem to be working at all for me - can't lock onto any satellites whatsoever. Not sure if it's a hardware issue since I never tested in Touchwiz, but if someone could try this app and see if they could pick up any satellites that would be a great help to sorting out this issue: https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en
3. Occasional graphical glitching whilst web browsing
4. Slight distortion from rear speaker (might just be my device)
5. Headphone output seems to be low (bit lower than my Note 1)
I flashed the latest nightly yesterday to find out that the data connection issue, at least on my phone, is still there. Ever since cm12 was launched the phone is most of the times off line when connected to the telephone provider.
Do you have the same problem? I find it really weird that even though this rom is continuously updated such a crucial problem hasn't been addressed in such a long time.
caravaggio971 said:
I flashed the latest nightly yesterday to find out that the data connection issue, at least on my phone, is still there. Ever since cm12 was launched the phone is most of the times off line when connected to the telephone provider.
Do you have the same problem? I find it really weird that even though this rom is continuously updated such a crucial problem hasn't been addressed in such a long time.
Click to expand...
Click to collapse
I'm getting 3g no problem on my device. No 4G in my area. Perhaps check your modem? Also has anyone had a chance to test the GPS on this ROM?
stephendt0 said:
2. GPS doesn't seem to be working at all for me - can't lock onto any satellites whatsoever. Not sure if it's a hardware issue since I never tested in Touchwiz, but if someone could try this app and see if they could pick up any satellites that would be a great help to sorting out this issue: https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en
Click to expand...
Click to collapse
Oh man, what a flashback. I disposed of a device because of this problem. This seem a fairly documented problem with the Note 2, with most solutions involving a warranty repair or exchange. Not only frustrating but also impossible for a second-hand device. I gave mine away only to accidentally find out while swapping the mid-frame with the silver bezel (to get rid of wear-and-tear / scratches) that the antennas were fubared! So in my case, after changing the mid-frame (which is cheap and fairly easy to do) the GPS signal came in perfectly. In any case, it's something to try.
stephendt0 said:
2. GPS doesn't seem to be working at all for me - can't lock onto any satellites whatsoever. Not sure if it's a hardware issue since I never tested in Touchwiz, but if someone could try this app and see if they could pick up any satellites that would be a great help to sorting out this issue: https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en
3. Occasional graphical glitching whilst web browsing
Click to expand...
Click to collapse
GPS doesnt work on my device either unless i change the setting to high accuracy instead of device only.
But after I flashed gps-fix.zip http://forum.xda-developers.com/showpost.php?p=58290777&postcount=47
it was working fine, at least on 0324 build.
---------- Post added at 02:56 PM ---------- Previous post was at 02:43 PM ----------
caravaggio971 said:
I flashed the latest nightly yesterday to find out that the data connection issue, at least on my phone, is still there. Ever since cm12 was launched the phone is most of the times off line when connected to the telephone provider.
Do you have the same problem? I find it really weird that even though this rom is continuously updated such a crucial problem hasn't been addressed in such a long time.
Click to expand...
Click to collapse
same problems here....
what i did was replacing libril-qc-qmi-1.so in system\lib\ with working ones from other roms such as nameless
and it was connected alright whether it's 3g or 4g......
derss123 said:
same problems here....
what i did was replacing libril-qc-qmi-1.so in system\lib\ with working ones from other roms such as nameless
and it was connected alright whether it's 3g or 4g......
Click to expand...
Click to collapse
In this case i dont see the point in installing the official ROM when other unofficial CM12 work out of the box and seem to be far better maintained than this one. Does anybody know why CM is not paying attention to this issue? N7105 is a fairly recent device and it used to work great with CM11. And it's not the only major bug I've been dealing with since I started testing CM12. I'm really frustrated
caravaggio971 said:
In this case i dont see the point in installing the official ROM when other unofficial CM12 work out of the box and seem to be far better maintained than this one. Does anybody know why CM is not paying attention to this issue? N7105 is a fairly recent device and it used to work great with CM11. And it's not the only major bug I've been dealing with since I started testing CM12. I'm really frustrated
Click to expand...
Click to collapse
I don't believe CyanogenMod has an active maintainer for t0lte, so the N7105 is just another untested supported device.
Edit: Good news is... sbrissen has uploaded a RIL fix for t0lte to the CyanogenMod gerrit, so hopefully, it'll be added to the official build soon.
Have a good one!
miji2 said:
Oh man, what a flashback. I disposed of a device because of this problem. This seem a fairly documented problem with the Note 2, with most solutions involving a warranty repair or exchange. Not only frustrating but also impossible for a second-hand device. I gave mine away only to accidentally find out while swapping the mid-frame with the silver bezel (to get rid of wear-and-tear / scratches) that the antennas were fubared! So in my case, after changing the mid-frame (which is cheap and fairly easy to do) the GPS signal came in perfectly. In any case, it's something to try.
Click to expand...
Click to collapse
derss123 said:
GPS doesnt work on my device either unless i change the setting to high accuracy instead of device only.
But after I flashed gps-fix.zip http://forum.xda-developers.com/showpost.php?p=58290777&postcount=47
it was working fine, at least on 0324 build.
[snip]
Click to expand...
Click to collapse
Thank you heaps, this worked perfect. I can now use my Note for GPS :good:
0327 build
viber video chat doesnt work ---
i could see the cam screen from the other end,
however when i turned mine on, the connection went suspended immediately.
Strangely enough, another messenger "LINE" got no trouble at all doing video talk.
Also tried on other cm12 based roms too, and viber video chat(cam from my end)couldnt be started up on any of them.
And i just googled to find out other devices have had the same issue on CM11/12 as well
All the messengers i use work great on stock rom 4.4.2
---------
really hope to see HDMI MHL output / Miracast working on cm based roms in the near future
.
derss123 said:
Anyone knows if low volume during calls being fixed on recent builds?
Also, how to enable HDMI output to TV ? Is this feature supported yet?
Thank you.
----------------+----------------
On 0324
Both issues above still ain't sorted.......
Also mobile data doesn't work, nor making/receiving calls....
Click to expand...
Click to collapse
I don't testet CM12 yet but on CM11 lowering and then raise the volume during the call fixed the low volume. If i call someone i just press volume down and then volume up at the start of a call.
HMDI output (MHL) is enabled by default but its not supported because of driver issues with Exynos. In CM10 & CM11 there was no support for it. I'd like to see support for this in the future but i don't know if this will ever happen.
derss123 said:
0327 build
viber video chat doesnt work ---
i could see the cam screen from the other end,
however when i turned mine on, the connection went suspended immediately.
Strangely enough, another messenger "LINE" got no trouble at all doing video talk.
Also tried on other cm12 based roms too, and viber video chat(cam from my end)couldnt be started up on any of them.
And i just googled to find out other devices have had the same issue on CM11/12 as well
All the messengers i use work great on stock rom 4.4.2
---------
really hope to see HDMI MHL output / Miracast working on cm based roms in the near future
.
Click to expand...
Click to collapse
Have you tried Google Hangouts? I think viber video chat is pretty buggy at the moment.
xhizorsz said:
I don't testet CM12 yet but on CM11 lowering and then raise the volume during the call fixed the low volume. If i call someone i just press volume down and then volume up at the start of a call.
HMDI output (MHL) is enabled by default but its not supported because of driver issues with Exynos. In CM10 & CM11 there was no support for it. I'd like to see support for this in the future but i don't know if this will ever happen.
Click to expand...
Click to collapse
Thank you for the reply
Well if it has something to do with drivers, i doubt it will be supported then......
But I noticed miracast is sort of working at the moment. I hope this feature will be improved soon.....
---------- Post added at 04:11 PM ---------- Previous post was at 04:03 PM ----------
stephendt0 said:
Have you tried Google Hangouts? I think viber video chat is pretty buggy at the moment.
Click to expand...
Click to collapse
oh no, never tried Hangout before
was on whatsapp / viber / LINE / kik most of the time......
I thought it could be viber's problem too as another messenger could do video chat ok .....
Just installed last night, really liking this rom. Today at 1:30pm battery was at 32%. Any tips on how to get better battery life? Also noticed there is no auto brightness, any fix for this?
Should I install latest Agni Kernel to get better battery like or no difference with it?
Thanks in advance.
pvaldeben said:
Just installed last night, really liking this rom. Today at 1:30pm battery was at 32%. Any tips on how to get better battery life? Also noticed there is no auto brightness, any fix for this?
Should I install latest Agni Kernel to get better battery like or no difference with it?
Thanks in advance.
Click to expand...
Click to collapse
Auto Brightness should now be Adaptive Brightness in CM12. Disable Adaptive Brightness to help with battery life a bit.
Have a good one!
derss123 said:
same problems here....
what i did was replacing libril-qc-qmi-1.so in system\lib\ with working ones from other roms such as nameless
and it was connected alright whether it's 3g or 4g......
Click to expand...
Click to collapse
i tried to replace that file with the same one from nameless. Result: no network at all, the icon is not even showing. How did you get it working?
---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------
AzraelsKiss said:
I don't believe CyanogenMod has an active maintainer for t0lte, so the N7105 is just another untested supported device.
Edit: Good news is... sbrissen has uploaded a RIL fix for t0lte to the CyanogenMod gerrit, so hopefully, it'll be added to the official build soon.
Have a good one!
Click to expand...
Click to collapse
Can you post the link where to download it from? Thanks!
caravaggio971 said:
Can you post the link where to download it from? Thanks!
Click to expand...
Click to collapse
It's possible that the changes will be in the next nightly. The download link will be the same as in OP.
Have a good one!
My Redmi Note 4X running the latest MIUI 7.7.13 only detects headphones plugged into the 3.5mm jack ONLY if the screen is on. If I turn the screen off and wait for about 15 seconds, the headphones are no longer detected after being plugged. The only way to have them detected again is to reboot the phone. I have this problem with Marshmallow and Nougat-based custom ROMs too. I have tried RR, AOSP, AEX... They all have the same bug.
I made a video as a proof that this BUG exists: https://youtu.be/dCpR4k4uaSg
Anyone? I don't believe that I am the only person experiencing this bug.
mura20 said:
Anyone? I don't believe that I am the only person experiencing this bug.
Click to expand...
Click to collapse
Well, I've an Indian variant (snapdragon) and I don't have any issues with headphone.
Sent from my mido using XDA Labs
Got the Snapdragon version. I had this issue also. I had to reboot the device to use my headphones ... after using it with lienage 6.0 and multi pro rom this issue is gone after using the phone for maybe 3 days. Now I dont need to reboot the device anymore to use my headphones.
But I got another issue with wifi ... It just wont connect to my home router when I type the correct password. (other networks are working fine...) - after a short time no using the phone it will automatically connect to the wifi itself ^^ strange things (on miui and lineage)
FroZine said:
Got the Snapdragon version. I had this issue also. I had to reboot the device to use my headphones ... after using it with lienage 6.0 and multi pro rom this issue is gone after using the phone for maybe 3 days. Now I dont need to reboot the device anymore to use my headphones.
But I got another issue with wifi ... It just wont connect to my home router when I type the correct password. (other networks are working fine...) - after a short time no using the phone it will automatically connect to the wifi itself ^^ strange things (on miui and lineage)
Click to expand...
Click to collapse
I knew someone else would also have this problem. Thanks for reporting!
So, according to you, headphones are detected on Lineage 13 (6.0) ? Strange because Lineage 14 (7.1) has this problem. What version of Multi Pro Rom has this issue fixed? Is it also based on Android 6.0? Thank you!
I use 8.2.5.0. On lineage (6.0) and multipro (6.0) the headphone is recognized for 90% of the time. Only once in maybe 2-3 days I need to reboot my device for using the headphones. In the first day of using a new rom I need to reboot it more often. I just don't know what's wrong with this issue
FroZine said:
I use 8.2.5.0. On lineage (6.0) and multipro (6.0) the headphone is recognized for 90% of the time. Only once in maybe 2-3 days I need to reboot my device for using the headphones. In the first day of using a new rom I need to reboot it more often. I just don't know what's wrong with this issue
Click to expand...
Click to collapse
Yeah, I have this issue with 8.2.5.0 too. It sucks to go back to Android 6.0 because of this issue. Why are you using 8.2.5.0 if it gives you detection problems?
I use Android 6.0 because of Xposed
I've created a BUG report in the MIUI forum. If you also have this headphone bug, please visit the link and hit confirm.
http://en.miui.com/thread-633924-1-1.html
@FroZine
Have you tried the newest AOSP Extended? The developer said that the headphone detection bug might be fixed....
mura20 said:
@FroZine
Have you tried the newest AOSP Extended? The developer said that the headphone detection bug might be fixed....
Click to expand...
Click to collapse
Yeah I use his rom for now and got no problems with the detection bug anymore. But I don´t buy a Xiaomi smartphone for not using MIUI But I will stay on his rom till xiaomi got fixed the problem with miui (I hope on marshmallow rom)
mura20 said:
@FroZine
Have you tried the newest AOSP Extended? The developer said that the headphone detection bug might be fixed....
Click to expand...
Click to collapse
Okay. Got the detection bug after 48h again. But only once. Its working better with AOSP Extended
sachin n said:
Well, I've an Indian variant (snapdragon) and I don't have any issues with headphone.
Sent from my mido using XDA Labs
Click to expand...
Click to collapse
which headphone or headset or handsfree ur using mine having issue i'm an Indian variant (SD)
kaushal7007 said:
which headphone or headset or handsfree ur using mine having issue i'm an Indian variant (SD)
Click to expand...
Click to collapse
I'm using an old samsung earphone. :/
No issues for me
sachin n said:
I'm using an old samsung earphone. :/
No issues for me
Click to expand...
Click to collapse
lol specific model no for that or u can suggest me new headphone for that i recently bought this: https://www.flipkart.com/soundmagic-es11s-wired-headset-mic/p/itmeux4gxcz3pu2b?pid=ACCEKECTECXRGR3H
Unfortunetly its not working in my phone only :crying:
kaushal7007 said:
lol specific model no for that or u can suggest me new headphone for that i recently bought this: https://www.flipkart.com/soundmagic-es11s-wired-headset-mic/p/itmeux4gxcz3pu2b?pid=ACCEKECTECXRGR3H
Unfortunetly its not working in my phone only :crying:
Click to expand...
Click to collapse
:crying: :crying:
Sorry mate! I dunno about earphones and never bought one... So... No idea. :/
You could ask fella members
Sorry again :/
I use this, don't laugh at me pl0x ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@kaushal7007 ^^
sachin n said:
I use this, don't laugh at me pl0x
View attachment 4183493
@kaushal7007 ^^
Click to expand...
Click to collapse
:highfive:
kaushal7007 said:
:highfive:
Click to expand...
Click to collapse
Mixed reaction xD :laugh: ::crying:
FroZine said:
Okay. Got the detection bug after 48h again. But only once. Its working better with AOSP Extended
Click to expand...
Click to collapse
I had the headphone bug on AOSP much earlier than 48hrs. This is so annoying! Xiaomi does not care about it. I have just installed 7.6.15 and the BUG persists!
The AOSP developer told me that the newest ROM had the issue solved but it didn't happen....