Related
Hi
Just updated to CM 12 nightly 20150123 and on rebooting got error "system UI has stopped" managed to get back into recovery and now installing backup of 20150122. Antone know what the problem is and if it can be fixed. TY
Stransky
Sent from my GT-I9505 using Tapatalk
Stransky said:
Hi
Just updated to CM 12 nightly 20150123 and on rebooting got error "system UI has stopped" managed to get back into recovery and now installing backup of 20150122. Antone know what the problem is and if it can be fixed. TY
Stransky
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Firstly, this is not the right place to pose this question. Secondly, I believe that this error is caused by recent commits to the framework source code. AFAIK it's been fixed and the next nightly should no longer have this problem.
Further to my previous. On CM 12 Nightly 20150124 and SD Card has been removed error is still happening. Can remount in CWM but error recurs after reboot.
Stransky
READ!!!
ME AND THE FORUM WE ARE NOT RESPONSIBLE FOR ANY BRICK, BOOTLOOP, SD CARDS DEATH, OR WAR TERMONUCLERARE, IF YOU HAVE PROBLEMS I AM HERE TO HELP, NOT JUDGE MY WORK THIS BAD, WE HAVE PUT TIME AND PASSION.
Hello Guys, today i ported the PAC-ROM for Galaxy S3 Neo, this ROM has not been tested on GT-I9300I!!!!
WHAT WORK:
ALL WORKS!!!
Bugs and ScreenShot you find them in the second and third post!!!
Instructions:
-Go in Recovery (Volume + button, button Central, Power Button)
-Wipe Data
-Wipe Cache
-Wipe Dalvik Cache
-Flash ROM
-Reboot System
-Again, go into recovery
-Flash Gapps
-Reboot System
LINK:
PAC-ROM FOR GALAXY S3 NEO
GAPPS
Do you like my work, Donate to me, to this e-mail -> [email protected] Thanks
CREDITS:
@Rox For CyanogenMod and Camera Fix
@AssoDiPicche for being based on your porting
CyanogenMod
PAC-ROM
XDA:DevDB Information
PAC-ROM PORTING BETA Galaxy S3 Neo, ROM for the Samsung Galaxy S3 Neo
Contributors
Danny_Dewet, Danny_Dewet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: All
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-04-15
Created 2015-04-15
Last Updated 2015-04-15
Reserved
SCREENSHOT:
Reserved
CHANGELOG:
15/04/2015
*Initial Release
NEXT VERSION:
---
BUG:
*com.android.phone crash (It does not happen at all)
*PAC Console Crash (it's normal)
*SystemUI Crash Firts Boot
FIX:
CAMERA FIX
Danny_Dewet said:
*com.android.phone crash
*PAC Console Crash (it's normal)
*SystemUI Crash Firts Boot
Click to expand...
Click to collapse
Thanks for this rom :cyclops:
a question: does "com.android.phone crash" mean the dialer isn't working ? can it be solved by installing alternative dialer from play store ?
WOW Installing ASAP,Thank you for porting Good Job
ricofear said:
WOW Installing ASAP,Thank you for porting Good Job
Click to expand...
Click to collapse
Thanks Bro
pad11 said:
Thanks for this rom :cyclops:
a question: does "com.android.phone crash" mean the dialer isn't working ? can it be solved by installing alternative dialer from play store ?
Click to expand...
Click to collapse
I do not know if the problem is on my SIM or Micro SD, because I read that this problem happens if you have a damaged SIM, I ask Rox.
Thanks for this port, testing it right now.
do I need to come from kitkat to flash this rom? Thanks
Marstradamus said:
Thanks for this port, testing it right now.
Click to expand...
Click to collapse
Thanks bro
badboyblue said:
do I need to come from kitkat to flash this rom? Thanks
Click to expand...
Click to collapse
No, Lollipop or KitKat
Danny_Dewet said:
Thanks bro
Click to expand...
Click to collapse
Tried this right now on my GT-I9301I (Stock Rom was the European Version - Italian Baseband I9301IXXUANF4 and the previous Rom before I tried yours, was the AICP Rom from jackeagle which has the Baseband I9301IXXUANF2).
I did each necessary step for flashing a rom except the reboot into recovery after flashing because I run every rom without GApps. After flashing the rom and booting it is impossible for me to get started with your PacRom cause my phone process crashes so rapidly that everything i can do i to click away the crash messages.
It crashes so fast that even a reboot is just possible trought removing the Battery. I´ll try this evening to flash the rom alongside with the GApps and report you the result. If you need some other Data just tell me what you need.
So have a nice day.
So does the phone app work or not? Its pretty useless without tat :/. Anyone can upload a logcat?
Marstradamus said:
Tried this right now on my GT-I9301I (Stock Rom was the European Version - Italian Baseband I9301IXXUANF4 and the previous Rom before I tried yours, was the AICP Rom from jackeagle which has the Baseband I9301IXXUANF2).
I did each necessary step for flashing a rom except the reboot into recovery after flashing because I run every rom without GApps. After flashing the rom and booting it is impossible for me to get started with your PacRom cause my phone process crashes so rapidly that everything i can do i to click away the crash messages.
It crashes so fast that even a reboot is just possible trought removing the Battery. I´ll try this evening to flash the rom alongside with the GApps and report you the result. If you need some other Data just tell me what you need.
So have a nice day.
Click to expand...
Click to collapse
I wrote them the Bug, this is a BETA, did not work the first Bluetooth, and SIM, will solve these problems, hopefully soon.
Danny_Dewet said:
I wrote them the Bug, this is a BETA, did not work the first Bluetooth, and SIM, will solve these problems, hopefully soon.
Click to expand...
Click to collapse
Right now I flashed it again and alongside withe the GAPPS and now the phone Apk is not crashing anymore. I will test a little more and if I found other Bugs I tell you.
Marstradamus said:
Right now I flashed it again and alongside withe the GAPPS and now the phone Apk is not crashing anymore. I will test a little more and if I found other Bugs I tell you.
Click to expand...
Click to collapse
OK thanks
Is there a really bad bug with PAC rom? I think this is at a very good state.
Sent from my GT-I9301I using XDA Free mobile app
Mike20017 said:
Is there a really bad bug with PAC rom? I think this is at a very good state.
Sent from my GT-I9301I using XDA Free mobile app
Click to expand...
Click to collapse
For some it might crash
com.android.phone
READ!!!
I warn you, from May 5 to 7, are the EXPO in Milan, so if we do not answer, you know why
Not working
Its not working dear with my Neo. TWRP says failed though I have the 2.8 version
Hi,
I recently flast the AOSB Kitkat rom (v 1.3.7) on my Galaxy Grand. I have noticed that the phone keeps rebooting many times when it tries to connect to a wifi network. There is no issue once connected or if wifi is off. But only during connection it reboots. I have tried clearing the cache and dalvik but it didn't help.
Any help would be appreciated.
ibshar said:
Hi,
I recently flast the AOSB Kitkat rom (v 1.3.7) on my Galaxy Grand. I have noticed that the phone keeps rebooting many times when it tries to connect to a wifi network. There is no issue once connected or if wifi is off. But only during connection it reboots. I have tried clearing the cache and dalvik but it didn't help.
Any help would be appreciated.
Click to expand...
Click to collapse
Try to flash cm12.1
I really like this ROM and don't want to move to lollipop. Any other option?
ibshar said:
I really like this ROM and don't want to move to lollipop. Any other option?
Click to expand...
Click to collapse
The random reboot is a bug and it never got fixed as dev stopped in 2014
If you want a kitkat rom then you could try AOGP, dev also stopped but it was my ro before switching to lollipop.
If you try AOGP don't get the last build as that had some serious problems, get one before that.
You can read about it in that thread.
This is the one aogp_i9082-KK-NIGHTLY-20141111-0421.zip
RichyE said:
The random reboot is a bug and it never got fixed as dev stopped in 2014
If you want a kitkat rom then you could try AOGP, dev also stopped but it was my ro before switching to lollipop.
If you try AOGP don't get the last build as that had some serious problems, get one before that.
You can read about it in that thread.
This is the one aogp_i9082-KK-NIGHTLY-20141111-0421.zip
Click to expand...
Click to collapse
Oh ok, thanks for the info... If all the kitkat roms have been discontinued, can you please point to a stable lollipop rom that does not have any major issues.
ibshar said:
Oh ok, thanks for the info... If all the kitkat roms have been discontinued, can you please point to a stable lollipop rom that does not have any major issues.
Click to expand...
Click to collapse
I would suggest at the moment AICP R2
After that BlissPop 5.1.1 V3.5 but this has at the moment some cosmetic problems and maybe you can better wait with that one until v3.6 is released
Hi,
I am facing some problems with my cyanogen 12.1 in my redmi 1s.
The last stable update i have is cm-12.1-20151002-UNOFFICIAL-armani.zip
After this i tried cm-12.1-20151129-UNOFFICIAL-armani.zip update and some updates before that. Then i tried the new 13.1 update. Every installation results in boot loop.
So now i installed MIUI7 and i really want to try cyanogen 13.
Anyone faced this problem ? Can anyone suggest a solution
elliot_robot said:
Hi,
I am facing some problems with my cyanogen 12.1 in my redmi 1s.
The last stable update i have is cm-12.1-20151002-UNOFFICIAL-armani.zip
After this i tried cm-12.1-20151129-UNOFFICIAL-armani.zip update and some updates before that. Then i tried the new 13.1 update. Every installation results in boot loop.
So now i installed MIUI7 and i really want to try cyanogen 13.
Anyone faced this problem ? Can anyone suggest a solution
Click to expand...
Click to collapse
Have you flashed the firmware zip from post #3?
I didn't understand. Can you give me the link to post
ok. i downloaded the firmware. why is this file needed? When should i flash this?
elliot_robot said:
ok. i downloaded the firmware. why is this file needed? When should i flash this?
Click to expand...
Click to collapse
It is needed because of the new kernel whick is based on kitkat.
Flash it before or after you flash the rom it doesn't really matter, and you don't need to flash it every time, just once.
Thanks :good:
i am also having same problem plz guid to solve...
cvele992 said:
It is needed because of the new kernel whick is based on kitkat.
Flash it before or after you flash the rom it doesn't really matter, and you don't need to flash it every time, just once.
Click to expand...
Click to collapse
i am also having same problem plz guid to solve...
smartyimrann said:
i am also having same problem plz guid to solve...
Click to expand...
Click to collapse
Everything is written up there, so just read it carefully!
Plz send me the link
Hi all, I'm just wondering if there are others that have similar issue than mine?
The problem is that after updating my phone to CM13 20160922 version and any newer version, the touch screen would not work anymore on the ROM. Touch screen would still work in recovery.
I've tried to clean wipe before installation of ROM and the same problem persists.
If it helps, when I tried to install a new kernel (Xcelerate one) on the working ROM, the touch screen would also break.
Any help would be appreciated.
Do a clean install (by wiping cache, system, data) if you havent, and see if it helps. Can only suggest to take full logs (incl dmesg, and lastkmsg) and fetch it to fefifofum on the respective thread. Is the behaviour consistent or random? I face it randomly but I guess mine is a hardware fault.
The behavior is consistent. It always breaks the touch screen on the newer roms. I'll try to fetch the logs and maybe it would help. Thanks.
Anyone can help me with getting logs without a touch screen? ADB can't seem to connect and the device is unauthorized. Thanks for any help.
Well you are not the only one. Its all about drivers in kernel. I changed my digitizer and then with 6 or 7 touchscreen does not work although all fine in TWRP 3.0.2 Someone has to port those drivers to new kernel used in Android 6. i have little knowledge about it but i will try to fix it and if it works i will post it here-
mobaddict said:
updating my phone to CM13 20160922 version and any newer version,
Click to expand...
Click to collapse
wait do you mean it was working on cm13 before those versions ???
bauuuuu said:
wait do you mean it was working on cm13 before those versions ???
Click to expand...
Click to collapse
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
... i will check
mobaddict said:
Yes, older CM13 version works. According to CM13 thread, it is the driver that doesn't work. I don't know how to fix the issue since this is a replacement screen and the driver works on older CM13.
Click to expand...
Click to collapse
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
bauuuuu said:
OK.. I found the issue and fixed it. Atleast on my phone now the touch screen is working. I do not know the characteristics of you changed touchscreen but i can give you newly compiled version of cm13. You can confirm me if thats working for you !
Click to expand...
Click to collapse
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
mobaddict said:
Okay. I can try. This is a replacement touch screen and is not an original one. I can try the compiled version that you made and see if that would fix the problem. Thanks
Click to expand...
Click to collapse
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
bauuuuu said:
https://github.com/armani-dev/andro...mmit/7687212b3b2c083ac1929d3957239c76098bd886 its merged in the main device tree so i hope all the builds (and not only cm13) henceforth will be ok. i didnt get the time to compile everything yet.
Click to expand...
Click to collapse
Thank you. I'll try to check if this would work.
mobaddict said:
Thank you. I'll try to check if this would work.
Click to expand...
Click to collapse
I'll just wait for a kernel build since I don't know how to do this hehe
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
debasarkar said:
I am also facing the same problem after replacing my original broken touchscreen. I am not able to upgrade my rom to cm-14.1. Please suggest some help.
Click to expand...
Click to collapse
I think we just need to wait for a new build of the kernel and test if this solves our problem. I'm also waiting for a kernel build and will test it out if this would fix the issue. :good:
I don't know if the commit that was made by @bauuuuu was used in the new build of CM14.1 but the latest rom still has the touch screen issue. The new TWRP 3.0.2-1 is now also facing the same problem.
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
mobaddict said:
Looking at the source of CM14.1 kernel, the commit used was there so this means that this modification did not fix the touch screen issue for my device. Hoping to be able to find another solution
Click to expand...
Click to collapse
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
bauuuuu said:
https://review.cyanogenmod.org/#/c/174024/
keep eye on new build there are more changes to match your touchscreen
Click to expand...
Click to collapse
Oh, wow! Hope that the 100Hz does the trick for my touchscreen and for others that are facing the same issue as me. Thank you for posting that. :good:
TWRP test build
Here is a test build for those with touchscreen issues. Please let me know if it works:
https://www.androidfilehost.com/?fid=313042859668276642