Q&A for [ROM][AOSP][Nightly/Release] CarbonRom KitKat [Hercules]
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][AOSP][Nightly/Release] CarbonRom KitKat [Hercules]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
No Audio On Phone Calls
The audio for phone calls don't work on this rom. I am running the most current version along with Wild Kernel #12. Anyone care to help?
Need help i'm having the boot loop with KitKat kernels .I told about this issue to Sultan XDA ..and he replied as
Tell those kernel devs to fix their keypad driver:
[ 109.012786] Unable to handle kernel NULL pointer dereference at virtual address 0000001c
[ 109.012969] pgd = d5f14000
[ 109.013061] [0000001c] *pgd=5594e831, *pte=00000000, *ppte=00000000
[ 109.013458] Internal error: Oops: 17 [#1] PREEMPT SMP
[ 109.013580] Modules linked in: dhd vibrator frandom
[ 109.013977] CPU: 1 Not tainted (3.0.101-stock++ #1)
[ 109.014099] PC is at sec_keypad_enable_show+0x10/0x24.
[ 109.014282] LR is at dev_attr_show+0x1c/0x48...so find my problem here: http://forum.xda-developers.com/gal...t-4-3-roms-t2999362/post58093351#post58093351
I askes for a fix and he replied :
Your keypad hardware is slow to initialize at boot:
[ * *1.250640] [TKEY] get_touchkey_firmware F/W version: 0x0, Module version:0x0
[ * *1.250762] f/w read fail retry 6
[ * *1.250946] EXT_I2C No ACK
So some of the data structs in the keypad driver remain in a null state until keypad probe can complete. Some of that data is accessed before keypad probe on your specific device can finish (so it is dereferencing null data), thus crashing the kernel. It's being caused by the keypad-disabler feature, which my kernel does not have. Sorry, but I'm not really interested in fixing other people's kernels, so I can't help you with that..... Can u fix this for me plzz!!
Related
Q&A for [GUIDE][Step-by-Step] Build ROM from source
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 [GUIDE][Step-by-Step] Build ROM from source. 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!
what can i do
Fetching projects: 99% (381/384) error: Cannot fetch shahjalalrasu/android_kernel_walton_primos2
shahjalalbwdb said:
Fetching projects: 99% (381/384) error: Cannot fetch shahjalalrasu/android_kernel_walton_primos2
Click to expand...
Click to collapse
Check the spelling of the repo.
It is saying it simply cannot find the repo you listed. So either its misspelled, not being directed to the correct location ie. Github.com, or it doesn't actually exist.
i faced that problem for build liquid smooth
build/core/product_config.mk:231: *** Can not locate config makefile for product "liquid_walton_primos2". Stop.
Your device was not found. Attempting to retrieve device repository from LiquidSmooth Github..
Traceback (most recent call last):
File "build/tools/roomservice.py", line 318, in <module>
fetch_device(device)
File "build/tools/roomservice.py", line 289, in fetch_device
git_data = search_github_for_device(device)
File "build/tools/roomservice.py", line 70, in search_github_for_device
check_repo_exists(git_data)
File "build/tools/roomservice.py", line 53, in check_repo_exists
"roomservice".format(device, android_team))
Exception: walton_primos2 not found in LiquidSmooth-Devices Github, exiting roomservice
ls: cannot access device/*/walton_primos2/liquid.mk: No such file or directory
build/core/product_config.mk:231: *** Can not locate config makefile for product "liquid_walton_primos2". Stop.
** Don't have a product spec for: 'liquid_walton_primos2'
** Do you have the right repo manifest?
[email protected]:~/liquid$
Need help i'm having the boot loop with KitKat kernels .I told about this issue to Sultan XDA ..and he replied as
Tell those kernel devs to fix their keypad driver:
[ 109.012786] Unable to handle kernel NULL pointer dereference at virtual address 0000001c
[ 109.012969] pgd = d5f14000
[ 109.013061] [0000001c] *pgd=5594e831, *pte=00000000, *ppte=00000000
[ 109.013458] Internal error: Oops: 17 [#1] PREEMPT SMP
[ 109.013580] Modules linked in: dhd vibrator frandom
[ 109.013977] CPU: 1 Not tainted (3.0.101-stock++ #1)
[ 109.014099] PC is at sec_keypad_enable_show+0x10/0x24.
[ 109.014282] LR is at dev_attr_show+0x1c/0x48...so find my problem here: http://forum.xda-developers.com/gal...t-4-3-roms-t2999362/post58093351#post58093351
I askes for a fix and he replied :
Your keypad hardware is slow to initialize at boot:
[ * *1.250640] [TKEY] get_touchkey_firmware F/W version: 0x0, Module version:0x0
[ * *1.250762] f/w read fail retry 6
[ * *1.250946] EXT_I2C No ACK
So some of the data structs in the keypad driver remain in a null state until keypad probe can complete. Some of that data is accessed before keypad probe on your specific device can finish (so it is dereferencing null data), thus crashing the kernel. It's being caused by the keypad-disabler feature, which my kernel does not have. Sorry, but I'm not really interested in fixing other people's kernels, so I can't help you with that........ Can any devs fix this for me plzz!!
Q&A for [KERNEL][LOLLIPOP][10.6.A.0.454][ADVANCED STOCK WITH RECOVERY](UB Only)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][LOLLIPOP][10.6.A.0.454][ADVANCED STOCK WITH RECOVERY](UB Only). 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!
Thank You!!!
Hey, dev!! Let me make a question for you: could I use this kernel with PA 5.1? Or is it just for specific 10.6.A.0.454 stock roms?
Tnx!!
C6503?
Thank You
Thanks a ton mate! It works and its super easy. Piece of cake..
i'm failed
20/029/2015 14:29:00 - INFO - Selected kernel (boot.img or kernel.sin): F:\Downloads\boot.img
20/029/2015 14:29:00 - INFO - Flashing selected kernel
20/029/2015 14:29:01 - INFO - sending 'boot' (14982 KB)...
20/029/2015 14:29:01 - INFO - OKAY [ 0.478s]
20/029/2015 14:29:01 - INFO - writing 'boot'...
20/029/2015 14:29:01 - INFO - FAILED (remote: Command not allowed)
20/029/2015 14:29:01 - INFO - finished. total time: 0.491s
20/029/2015 14:29:01 - INFO - FASTBOOT Output:
sending 'boot' (14982 KB)...
OKAY [ 0.478s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.491s
Click to expand...
Click to collapse
[Q&A] [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015
Q&A for [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UNOFFICIAL][5.1.1_r13]BlissPop 3.9 by Team Bliss UBERTC 4.9 19/08/2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
it has s2w?
Great work muucho gracias
, y'a it's has s2w on kernel setting
can't turn on wifi after soft reboot :
E/WifiMonitor( 9156): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown ini
t.svc.p2p_supplicant=unknown
E/WifiHW ( 9156): failed to translate ifname to idx
E/WifiHW ( 9156): could not remove P2P interface: -19
E/WifiHW ( 9156): Wi-Fi - could not remove p2p interface
D/WifiMonitor( 9156): startMonitoring(wlan0) with mConnected = false
E/WifiHW ( 9156): Unable to open connection to supplicant on "@android:wpa_": N
o such file or directory
after a normal reboot it's work
Super Rome so far!
I have only one problem, my email with k9 not be retrieved automatically with Pusch
It is possible to activate Double Tap2wake?
Gesendet von meinem One X mit Tapatalk
I have suddenly poweroff device and go to bootloop. When MIUI bootanimation start .
I try all Guide available here and there but still not work.
I can access Recovery and internal Storage but when try to boot rom it goes bootloop .
I try Miui and aosp rom but still .
My kernel log have this :
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.117-perf+ ([email protected]) (clang version 8.0.12 for Android NDK) #1 SMP PREEMPT Wed Dec 9 11:21:40 CST 2020
[ 0.000000] Boot CPU: AArch64 Processor [51af8014]
[ 0.000000] Powerup reason=0x80081
[ 0.000000] Machine: Qualcomm Technologies, Inc. trinket pm6125 + pmi632 IDP
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] OF: reserved mem: OVERLAP DETECTED!
Click to expand...
Click to collapse
Please Help me and thanks alot .
THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Kindly use the existing thread for continuing discussion: https://forum.xda-developers.com/t/help-in-bootloop.4333531/
Regards,
shadowstep
Forum Moderator