Chargig issue on 4.4 bootloader - Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti

Hi im new to the note 8 and foolishly updated to the latest kitkat before flashing aosp & cm roms but now when device is off the screen wont turn off and it doesnt seem to be charging (but it does when switched on)
I understand this is an issue with the new bootloader however is there a fix for this or a specific cm/aosp rom that works without the charging issue?
In the meantime I'm stuck on stock tw so any help would be greatly appreciated
Sent from my GT-N5110 using Tapatalk

Anyone? ?????
Sent from my GT-N5110

1eyedmonster said:
Hi im new to the note 8 and foolishly updated to the latest kitkat before flashing aosp & cm roms but now when device is off the screen wont turn off and it doesnt seem to be charging (but it does when switched on)
I understand this is an issue with the new bootloader however is there a fix for this or a specific cm/aosp rom that works without the charging issue?
In the meantime I'm stuck on stock tw so any help would be greatly appreciated
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Have you tried the latest nightly? From what I have read other CM11 based roms fixed this issue back in July and from reading the thread for the N8 it almost seems as if they fixed the issue as well. It would make sense that if CM11 for another Note device has this fixed that it was carried over.
I'm don't know for sure just relaying what I have read.

CCallahan said:
Have you tried the latest nightly? From what I have read other CM11 based roms fixed this issue back in July and from reading the thread for the N8 it almost seems as if they fixed the issue as well. It would make sense that if CM11 for another Note device has this fixed that it was carried over.
I'm don't know for sure just relaying what I have read.
Click to expand...
Click to collapse
{
"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"
}
not working pal
Sent from my GT-I9505

CCallahan said:
Have you tried the latest nightly? From what I have read other CM11 based roms fixed this issue back in July and from reading the thread for the N8 it almost seems as if they fixed the issue as well. It would make sense that if CM11 for another Note device has this fixed that it was carried over.
I'm don't know for sure just relaying what I have read.
Click to expand...
Click to collapse
I had posted this issue in a few places hoping somebody would know a fix and I can't thank the developer enough for the time he spent in fixing here is the fix http://forum.xda-developers.com/showthread.php?p=55714042
Sent from my GT-I9505

Related

I have an issue with kernels and my camera, I hope someone can chime in.

Hey guys and gals
I'm having a lot issues with roms that are being developed. From my understanding hardware versions 0004 are phones who seem to be having issues with the camera. That's not my case. I'm currently running 0003 and experiencing issues with my camera with just about every Rom I load that doesn't use a certain kernel.
For example - earlier today I loaded frost aosp Rom and really wanted to run it, but it uses a custom kernel which my phone doesn't like. I tried flashing the OTA kernel which is in the wiki and that too didn't work.
From what it seems and what I have tested is that the following kernel is about the only one that works for me.
{
"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"
}
I know people have been able to solve this by removing their battery for a while and I don't understand how that works for people. Upon trying it and rebooting my phone still has a broken cam.
If I can get any input on this I would greatly appreciate it.
Sent from my PC36100 using XDA App
I know that I have read somewhere that even some of the late 003 Hardware version EVO's have the same issue you have. Just a stab in the dark but have you tried the special version of Amon for 004 Hardware users. This supposedly fixes problems people were having flashing custom roms and kernels.
Stab in the dark but it may help you
I have not. I mean I'm running recovery 1.8 what else should I be doing? Would you be able to point me in the right direction?
Sent from my PC36100 using XDA App
You may find this discussion of interest:
Jbcarrera said:
... any phone with new camera hardware has to use stock kernel 10 or 17. htc hasn't released the source code for those kernels so there are no custom kernels for them yet
Click to expand...
Click to collapse
Well I figured that was the issue. Any idea when the sources for those will be released?
Sent from my PC36100 using XDA App
HTC Stock Kernels for new EVO's
B4 I FU RU 18 said:
Well I figured that was the issue. Any idea when the sources for those will be released?
Click to expand...
Click to collapse
Nope, that's up to HTC.
#10 is here:
ricsim78 said:
Kernels:
Stock HTC #10 kernel (from 3.30.651.2 OTA)]For those who have phones that only like stock kernels, flash this.
Click to expand...
Click to collapse
Let me look around & I'll find #17..
Here, from: 2.2 ultimate kernel review
skydeaner has them on his site: Evo Benchers!
Kernel Downloads
Awesome! I figured just as much but wanted to see what xda thought of it all.
Thanks
Sent from my PC36100 using XDA App

[Q] Caller ID showing weird symbols

So I am having an issue where my caller id from people not in my contact list is just showing weird symbols.
http://postimage.org/image/jq6n7ftuv/ - here is the image as it wont let me embed it currently.
As you can sww just weird symbols.
I am currently on CM10.0 with the KT747 kernel. I have tried different kernels and different roms to no avail. I believe the problem started when I flashed the AOKP rom but I am not 100% sure.
I have tried wiping everything and installing just CM10 and that did not work. I am not sure what else to try.
I am having this issue as well. I have also used several roms and kernels however this issue persists. Currently using i747z rom on Rogers.
That's actually kind of cool lol
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
{
"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"
}
tdunks said:
So I am having an issue where my caller id from people not in my contact list is just showing weird symbols.
http://postimage.org/image/jq6n7ftuv/ - here is the image as it wont let me embed it currently.
As you can sww just weird symbols.
I am currently on CM10.0 with the KT747 kernel. I have tried different kernels and different roms to no avail. I believe the problem started when I flashed the AOKP rom but I am not 100% sure.
I have tried wiping everything and installing just CM10 and that did not work. I am not sure what else to try.
Click to expand...
Click to collapse
Have you tried to Odin back to completely stock?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I only noticed this recently (early December). Do you think a restore of a nandroid backup previous to December would fix this issue?
Kipp34 said:
I only noticed this recently (early December). Do you think a restore of a nandroid backup previous to December would fix this issue?
Click to expand...
Click to collapse
It's worth a try.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I am seeing this on my LG P930 (Bell Optimus LTE) on CM10.1 (2/21 nightly) unlocked and connected to Rogers network.
I read, somewhere, that this is a problem on Rogers devices that are not using stock ROM's. And yes, I too have this issue running a 4.2.2 ROM.
Flash a different modem. That will fix the issue.
There is another thread here with people having the same issue and it was the modem. So before you start wiping everything flash a new modem first and see how it goes.
Sent from my SGH-I747 using Tapatalk 2

[Q] Jagged/Low Res Display - Multiple ROMS

Hey everyone! Thanks in advance for helping.
I've been running a CM9 nightly from Dec 23rd for a while now, being too busy to change.
Yesterday, I backed up everything and did a full reset (factory, cache, dalvik) and flashed the latest LiquidSmooth ROM and the gapps package they have in the thread. Restarting the first time, the liquidsmooth logo just kept going during boot and never sent me into the OS, which isn't unheard of, so I just held the power and hoped nothing bad happened. On the next reboot, everything was fine.
Here's where the problem started: The little curves and detailing on everything, from the type to the app icons to any image, all looked jagged! The battery indicator circle in particular looked terrible. Now mind you, everything worked fine and was entirely usable, but the fine edges just cut into my eyes.
So, I reset everything again, and glashed the latest CM10.1 Wild in the Night. Same exact look! Sorry I don't have images, but I took screenshots and I ran into another problem with the media process freaking out on the ROM.
Here's the kicker: I restored my CWM backup, and CM9 looks perfect. Maybe it's AA or something? Not sure. Any tips? Thanks!
Flash back to stock and see if that fixes it.
{
"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"
}
Its a CM10.1 kernel issue. So it will affect roms that use the same kernel, which is everything AOSP 4.2.
TW jellybean, or anything ICS or older will not have the issue.
Adreaver said:
Its a CM10.1 kernel issue. So it will affect roms that use the same kernel, which is everything AOSP 4.2.
TW jellybean, or anything ICS or older will not have the issue.
Click to expand...
Click to collapse
Ah, so everyone else on AOSP 4.2 is having the same issue? Or is it just a known bug that some encounter? If that's the case then I guess I just find the best JB ROM for now.
The odd thing is thta I've googled around with multiple keywords and no one else has mentioned it, although I may be using the wrong terms.
Fencefry said:
Ah, so everyone else on AOSP 4.2 is having the same issue? Or is it just a known bug that some encounter? If that's the case then I guess I just find the best JB ROM for now.
The odd thing is thta I've googled around with multiple keywords and no one else has mentioned it, although I may be using the wrong terms.
Click to expand...
Click to collapse
I'm not seeing this issue on the newest pacman from a few hours ago. I imagine other aosp ROMs will soon follow.
Sent from my Epic 4g Touch on PACman

[DEV] CyanogenMod 13 port to SM-G920P

I have begun to work on setting up a device tree for the sprint version of the Samsung Galaxy s6
Many people probably have noticed that arter97, sktjdgns1189, tdcfpp, and RaymanFX , have been working on porting CyanogenMod to the Galaxy S6.
They have been working on the international flat variant. The source code has been released. I will try my best to port the ROM to our device variant and I will keep this thread updated as I go.
If you have any questions at all about CM on the S6, I will try to answer them or find an answer to them.
If anyone is interested in helping out with this please contact me on here or on hangouts my email is [email protected]
Im hoping to have a build completed and ready for testing soon.
I have created a GitHub repo for the SM-G920P https://github.com/SamsungGalaxyS6
Thanks, do note that touch didn't work when flashing original cm13 (device asserts removed from updater-script.
CrazyJ36 said:
Thanks, do note that touch didn't work when flashing original cm13 (device asserts removed from updater-script.
Click to expand...
Click to collapse
You were able to flash the international version and have it boot up when you removed the device asserts??
Can you let me no what else worked and what didn't work
Please only open threads when you have something to release for users to flash/test.
Placeholders are not a thing on XDA.
I have finished a build for the 920P but have not been able to test it yet because im stuck at work so im not going to post a link yet but if anyone would like to be the first to test this build please send me a message and i will send you the zip file. If not i will test when i get home
thanks
mtb3000gt said:
You were able to flash the international version and have it boot up when you removed the device asserts??
Can you let me no what else worked and what didn't work
Click to expand...
Click to collapse
Yes that's the only change I made.
I didn't test much, though
For Hardware Nav buttons, home worked, long press home for recents worked
Hardware back did not work.
enbling navbar in build prop worked fine.
Camera not found.
No sim found
Wifi worked
Working:
Everything
Not working:
Camera (Front, Back)
Cellular
{
"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"
}
Is there any way to compile remotely?
Sent from my SM-G920P using Tapatalk
asafegous said:
Is there any way to compile remotely?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
SSH into a Linux machine, or an online Linux box.
I'm interested in this
This has got to be the longest time ive been without cm ever.
Sent from my SM-G920P using Tapatalk
I am closing this thread and have opened a new thread with download links available
http://forum.xda-developers.com/spr...om-cyanogenmod-13-galaxy-s6-sm-g920p-t3272289
Could you possibly upload the 6.0 icons?

Cm 13 beta

{
"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://galaxynote3root.com/sm-n9005...marshmallow-root-for-galaxy-note-3-cm13-beta/
http://m.youtube.com/watch?v=wdzN6MatxTA
For those of *you looking for Android 6.0 Marshmallow and root for your Galaxy Note 3, we finally have a beta version of CM13!
Now, this is still WIP (Work in Progress) as almost everything is working except phone calls, the ROM does NOT recognize SIM cards. * But if you want to try all of the Android 6.0 Marshmallow features, you can easily make a backup ROM of your current ROM, try out the ROM, then revert back to your working ROM.
This CM13 beta version actually runs very smooth, fast and you will be able to experience latest Android 6.0 features like new DOZE feature that will extend the battery when you are not using your phone, advanced permissions control for apps, dedicated memory settings, and much more.
Overall, I would say stable versions are not too far away and if you want to try out Android 6.0 Marshmallow on your Note 3, just flash away and do let me know what you think!
Sent from my SM-N900T using Tapatalk
That page is pretty outdated. There are decently stable versions of CM13 now available in the main note3 forum:
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
http://forum.xda-developers.com/galaxy-note-3/development/rom-unofficial-cyanogenmod-13-0-t3238064
frequentc said:
That page is pretty outdated. There are decently stable versions of CM13 now available in the main note3 forum:
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
http://forum.xda-developers.com/galaxy-note-3/development/rom-unofficial-cyanogenmod-13-0-t3238064
Click to expand...
Click to collapse
Your link is deleted
Sent from my SM-N900T using Tapatalk
lox2013 said:
Your link is deleted
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Both links work. I think it's a tapatalk problem. I've heard others mention the same problem.
frequentc said:
Both links work. I think it's a tapatalk problem. I've heard others mention the same problem.
Click to expand...
Click to collapse
I check now
Sent from my SM-N900T using Tapatalk

Categories

Resources