Hi there,
trying myself on compiling my "own" PA Build for my HTC one.
Basically i found everything i needed and get the build completed.
Compared to the builds from @slick_rick, my look very similar.
But after installing the rom on my One it reboots after a couple of seconds while updating the apps.
So i wiped the one and tried again. I could select the language and hit next. Again reboot.
Already switched from BBQ Linux to Ubuntu, but the problem stayed the same
Any help is appreciated. Maybe someone can point me a direction where to find somekind of logfile,as adb does not seem to be activated that early after device boot/initial setup.
THX
Chaos
Related
Hello,
I am trying to port this rom
http://forum.xda-developers.com/showthread.php?t=1090186
to our device but always stuck on symlink error.
In this rom everything is working fine, my cousin ported this on his hero.
I am trying to port this from android kitchen, porting tools, port device from other rom.
I read many thread tried way but nothing can help it out. tried to extract kernel from gsb, condemnedsoul rom, but still getting error.
I have tried with update script, in which it stuck on boot.
any help will be appreciated.
have you by chance tried moving the recovery log to the SD card and checking it? I'm still new at the game as well but I was having some kitchen issues myself being so fresh to it and under the Troubleshooting it directs one to use the Recovery Menu to move the recovery.log to the SD card so that you can push it to your computer for review of any errors that occurred during flashing. I myself have just done this a couple of hours ago. If you can't tell yourself what went wrong that needs fixing in hte recovery.log ask a seasoned dev. they sure are helpful
no no
no no not. I will try it out now, will post logs here.
I would love to see this rom ported to the Eris, keep it up
guys ported this
Hello,
I ported this on eris. I am testing it. anyone interested in testing this?
please let me know.
Thanks.
wifi
calls working,
bluetooth working,
camera working,
video recording working,
powerdown working,
stuck on wifi, doesnt work.
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
theking1st said:
Hi guys. It is my first time to run cyanogenmod on my phone. I have the Samsung Galaxy Exhibit 2 4G and I tried to install the CM 11 of jfbs. I did all the backups and I wiped the data and cache and installed the ROM and Gapps. But I rebooted my device and the Cyanogenmod logo appeared with the spinning arrow and it didn't want to stop spinning (or loading if you want). My phone was stuck on logo and the spinning arrow. I forced the phone to turn off and when I rebooted it I worked but after a little time it went back to the logo and the spinning arrow. I re-installed the ROM and Gapps but like before, the logo and the spinning arrow still there until now and it won't even stop and lead me to the lock screen. PLEASE can somebody tell me if it won't work or what is wrong whit it or if it is matter of time, how long should i wait? PLEASE I need to know what is going on and what to do. :crying:
Click to expand...
Click to collapse
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
cars1189 said:
(as a dev for this phone)
If you could PM me with more details that would be helpful. When i hear that it continues after a reboot(not the first person to have said that) i think its that you are not waiting enough time. That may or may not be the case. I would give it a good 5 min. I have never timed mine but it does seem to me that prior android versions took about 2-3min maybe and for w.e. reason android 4.4(cm-11.0) takes a few more min. Anything over >=10min though id say is too much. In these cases the only things that can really help are logs. Logs are the only way you can show a dev what you are experiencing.
(as a xda member)
Also i would use the device thread not the general android thread, read through the rom thread of the rom you are tryng to install, and a last and final note, I would recommend that anyone that is new to install older more mature roms first. These roms will yield the best experience in most cases. Then once you are familiar you can experiment with other roms/mods etc etc.
Click to expand...
Click to collapse
Thank you @cars1189 for your answer. I used the device thread to do it but the problem is, I let it spinning for more than 5 hours. I have flashed many roms in my phone since i had it (more than 10 times or more) and i know that it does not take more than 10 mins max to install. But don't worry after that i went back and restored my previous CM 9 rom and right now i'm on the CM 11 build of 1-29-14 of your CM mass thread. It works fine, not at 100% but it doesn't drain my battery like your CM 10.2 build of 1-11-14 and it is almost stable. I will try tonight to use your ADC kernel with the jfbs CM 11 rom that first didn't work for me because I saw in your thread that this kernel may help it to load and install without the spinning issue. So i will give it a shoot. But anyways thanks for your answer and it means a lot to me really. :good:
GOOD
@cars1189 , I'm actually running the 6-18-14 build of CM11 and as far as it goes, i'm not encountering any major issue at the moment. The theme engine is working fine for me and battery life is great for my usage. I use this build as a daily driver, and it does a great job. Calls, texts, data, wifi, Bluetooth and GPS are all working. I had issues before with the amount of RAM available, but now that it has 375MB of RAM, it is more snappy. Just :good: Thank you for your work on our to make our phone still valuable today!! THANKS MAN!!!!!!
Hi Guys,
I'm currently in the process of building AOSP to just flash a basic image onto a Nexus 7.
I've done the "repo sync" to get all the relative files, and have initialized the build environment exactly as the tutorials on the Android development site asks, including downloading proprietary drivers, however whenever i'm trying to do my first "make", it either gives me an error saying a random make file received a kill signal, or my machine just freezes.
As of writing this a build has been going for 7 hours (Is this normal?) and the machine just freezes up.
Any help/advice would be greatly appreciated, i'm unsure of how to try and fix what's happening
Jay
Hello,
First, I want to say that I hope this is in the right subforum. Otherwise, please, move this thread.
So I have a big issue with using Cyanogenmod 12 and 13 on two totally different devices; the international version of Samsung's Galaxy S4, and the OnePlus One. Installing either version of Cyanogenmod works perfect, but as soon as OpenGApps is flashed (Tried nano, pico...) and Android is loaded up, it gets stuck in an infinite stream of crash messages, telling me that "Unfortunately, the process com.google.process.gapps has stopped."
I have found a fix. BUT this only works on CM13. If you click-spam your way through the first time launcher, then navigate to Settings and find System Restore and perform said operation, then the crashes with magically go away and the phone will run without any problems at all. This is good enough for my OnePlus One.
However: There is no stable build of CM13 for the Galaxy S4 international, in the latest Nightly-build I tried for it, call audio was not working at all.
Does anyone know why this is happening, and how do I go about fixing this, other than the solution I found above?
Help is much appreciated!
I really suspect it being an OpenGApps issue. Though I do not understand why as the same build/phone has worked fine with it before.
Are there any reliable alternatives?
Hi all!
I have already commented on a opened thread about this problem but, as it was a similar, not exactly the same problem, I decided to make a new one, and delete the comment. I tried to install AOKP osprey nougat on my Moto G 2015. It installed with no problem at all, I installed it with Magisk and OpenGapps micro. But, as soon as the phone turned on and I started to go through google registration stuff, I started get a "advanced settings has stopped" with a close button. It was happening forever. I could fast click close and do one click on the phone but the error message was popping up every second. It was unusable, forcing me to not use aokp custom rom. I'm waiting for a new release. U guys do an awesome job and I would love to be able to use it on my phone...
Ty.
:crying:
Hello again guys! A new aokp Osprey version has been released in 05/23. I tried it in my Moto G 2015 that was running LineageOs with no problems. Just like the older ones it installed fine with gapps. But the further problems that I had with the older versions happened again. In the first boot, after installation, the popup error, that I talked about in the previous post appeared, but, this time I managed to get rid of it by just closing it some times (approx. 20x), so then I could login to my google account. In this first boot the phone was working fine, I installed some apps, changed some configs, and it seemed to be working ok. I decided to reboot my phone for testing purposes and here is where stuff broke again. The same error popup that I talked about, but now even with me closing it for at least a hundred times the popup was showing everytime. So, saddly, I just had to return to LineageOS.
That's it, bugs are still happening... But keep up with ur good work and, hopefully we will have some amazing Osprey ROM in te future.
Same bugs...
New ROM (aokp_osprey_nougat_nightly_2019-06-06_ota.zip), same bugs...
I'm giving up on AOKP for now...