CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 10.2 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Useful Links
BBQLog changelog
Odin CyanogenMod wiki
Jira issue tracker
DO NOT REPORT BUGS FOR UNOFFICIAL BUILDS!
Other Issues?
Use this for obtaining logs.
These are unofficial beta builds so bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
Download Links
CyanogenMod:
Builds: http://goo.im/devs/mithun46/CM4.3
Google apps addon:
Download: 4.3 Google Apps
Root access:
Go to Developer options --> Root Access
And change to "Apps and ADB" to fix root
Screenshots: 1, 2 & 3
Thanks to:
CyanogenMod: Thanks a lot! You guys are awesome!!
@jug6ernaut : For being a awesome friend! Thanks man!
Reserved
Sweet! Downloading now!
If I'm on stock rom, Do I just follow the OP instruction?
motoxxxx said:
If I'm on stock rom, Do I just follow the OP instruction?
Click to expand...
Click to collapse
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
havanahjoe said:
Pretty much. Do you already have a recovery installed? You need to have an unlocked bootloader as well.
Click to expand...
Click to collapse
Thank! now I need to unlocked my bootloader.
How is the rom?
motoxxxx said:
Thank! now I need to unlocked my bootloader.
How is the rom?
Click to expand...
Click to collapse
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Titanium Backup > Menu > Preferences > Backup Folder Location > DETECT > Whole Device > Select /storage/emulated/legacy/titaniumbackup and click yes when prompted to move backup files.
Click to expand...
Click to collapse
Looks like it works without doing that last step.
And in case you are trying to get into recovery, reboot and when you see the LED flash orange, hold the volume down button. Thanks mithun for the help
havanahjoe said:
I just installed it, looks good so far. Forgot to flash the superSU zip so I don't have root yet. Trying to figure out how to get into recovery after flashing.
If you are going to be restoring a Titanium Backup, there is a known issue on 4.3 where you have to change the backup folder location.
From the Nexus 4 thread:
Click to expand...
Click to collapse
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
jug6ernaut said:
Three otpions
1. Reboot phone, press volume down when you see the notification led go orange.
2. Advance reboot menu
3. From adb "adb reboot recovery"
Click to expand...
Click to collapse
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Enable developer options. (go to about phone, scroll to the bottom, find the “build number” field, click on it seven times and it will turn on developer options.)
go back one level to the main settings screen and you’ll see developer options now. Open that, Enable advanced reboot options by clicking on the relevant checkbox
Click to expand...
Click to collapse
havanahjoe said:
Thanks jug6ernaut. Advanced reboot menu is not enabled by default. I had to look up where to enable it:
Click to expand...
Click to collapse
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
jug6ernaut said:
True , which are under developer options for anyone wondering!
Small update for anyone who saw my "issue list" in the other CM thread. Almost all of my issues were caused by using the wrong gapps(was unaware there was a 4.3 version).
Im up on 4.3 again and its working beautifully , still few performance and graphical issues, but they are minor.
Edit: Cant get SMS to send, guessing this has to do with the Voice+ addition as MMS send fine. Can also receive MMS and SMS fine, just cant send SMS.
Click to expand...
Click to collapse
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
havanahjoe said:
Hmm I am running into the same issue with SMS, can't send.
I don't see the group MMS option in the stock messaging app. The Nexus 4 has it, so is this not the same Messaging app as the Nexus?
Click to expand...
Click to collapse
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
jug6ernaut said:
idk if this is an issue with CM for the ZL or what. Or if its my sim card. Plain and simple IDK.
BUT for me this is caused by my sim not having my phone number, the messaging app will not show the group messaging option if it does not know your number. To check this go to you phone settings/About Phone/Status/Phone number. Mine would show "UNKNOWN". To fix this after every flash i have to run a program called "Sim Number Changer", its an Xpoxed app. It worked for me.
Click to expand...
Click to collapse
Ah yes. I had noticed that in my status page before, but didn't know it broke the Group MMS option. I'll use the Sim Number Changer.
I asked in the Z thread to see if they are having issues with SMS too.
EDIT: Sim Number Changer FCs on me
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
{
"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"
}
havanahjoe said:
The Z users are able to send SMS, but they mentioned the HTC One had the problem. I looked in their threads and it's apparently gone in a new build.
I did a logcat and didn't see any errors when sending a message, other than chompsms telling me the message failed (and this I already had seen on the phone). The error message doesn't explain why.
---------- Post added at 05:16 PM ---------- Previous post was at 04:34 PM ----------
I don't like my phone showing up as a 6503 A quick build.prop edit fixes that.
Click to expand...
Click to collapse
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Haha nice!
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
A little off topic, do you have the new Nexus 7?
havanahjoe said:
A little off topic, do you have the new Nexus 7?
Click to expand...
Click to collapse
I do .
jug6ernaut said:
I do .
Click to expand...
Click to collapse
The million dollar question is... Is it worth the upgrade from the original 7?
havanahjoe said:
The million dollar question is... Is it worth the upgrade from the original 7?
Click to expand...
Click to collapse
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
jug6ernaut said:
Tough question. I sold my original nexus 7 few months back in preparation for the new one. So for me its 100% worth it lol. Kind of hard for me to judge it the old model BC I don't have them side by side.
Buy I will say this thing is FAST. Screen is amazing, absolutely love it. Was thinking I would hate the space above/below the screen, don't mind it. Definitely thinner tho, its noticeable, also smaller side bezel is nice. One thing not getting a lot of attention is the speakers are definitely a step up from the original which were just poor.
Really the big thing for me is the screen, it really is a big improvement. Absolutely beautiful.
Is it worth it? Who knows, I say yes. I mean at the price it was hard to say no. If you have the original and your happy with it the new one isn't going to be anything ground breaking. But if you have the cash, it is a worthy upgrade.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick review. I really don't have a lot of use for a tablet myself, I have my laptop with me almost all the time and I don't mind carrying it (even though it's a 17" MBP), but I have been considering using a Nexus 7 as Nav/Media in the car. I've seen several people with a Subaru Legacy do it on theirs and it seems to fit very well. In that case the screen wouldn't really matter that much and doing a quick search on craigslist I found a 16 GB for $100. With what you said, it seems like a no brainer to get the first gen.
Apologies for the off topic discussion. To bring it back to CM, I am currently building a copy myself. Thanks to mithun I got my Ubuntu VM ready for compiling and it's CCing away.
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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. Hard. A lot.
*/
PREVIEW DISCLAIMER:
This is a PREVIEW : CyanogenMod 10 is nowhere near ready to be used as a daily driver (lots of features still have to be merged), and same is the device support. CHECK THE KNOWN ISSUES LIST BEFORE THINKING ABOUT POSTING.
IF YOU ARE *****ING WITH "When this will be fixed!!!!?????" THEN I'LL JUST CLOSE THE THREAD AND YOU'LL HAVE TO WAIT EVEN MORE.
DISCUSSION THREAD: http://forum.xda-developers.com/showthread.php?p=30744835
IF YOU WANT TO SAY THANKS, HELLO, ASK ABOUT YOUR KERNEL, ISSUES WITHOUT LOG, OR HAVE SEX, THAT'S THE THREAD TO USE!
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
KNOWN ISSUES
Click to expand...
Click to collapse
- FMradio, heh!
- Camera is unstable, though taking pics should work
- Wi-Fi tethering is semi-broken
- Some audio issues #blamecodeworkx
TIPS & TRICKS
Click to expand...
Click to collapse
- Camera is now part of Gallery, that's why you might have two (because of Gapps)
- If you have no Camera icon in app drawer, remember you have a lockscreen
- If one camera app doesn't work, try the other one (if you have two)
- If it worked once then didn't work anymore, reboot
HOW TO INSTALL
Click to expand...
Click to collapse
- Download the zip
- Download Gapps
- Install the update zip from recovery
- Install gapps from recovery
- Wipe/Factory reset
- Reboot
SCREENSHOTS
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"
}
SUPPORT
Click to expand...
Click to collapse
If you're encountering a bug that isn't listed above, make sure to attach a logcat with your report. If you don't know how to do it, then refrain from posting. Once again, if this thread is becoming a hassle for me, then I'll close it right away. And remember that CM10 IS A WORK IN PROGRESS. No complaints for missing features either.
You can check out #teamhacksung-support on Freenode for live support - but we won't hesitate to ban you if you're *****ing.
Also, a donation on the www.teamhacksung.org webpage is really appreciated. Thanks!
reserved for entropy's house of n8013
Didnt see a mention of the pen. Do you believe it will work with CM10?
Sent from my GT-N8013 using Tapatalk 2
mitchellvii said:
Didnt see a mention of the pen. Do you believe it will work with CM10?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
It is working, yes
mitchellvii said:
Didnt see a mention of the pen. Do you believe it will work with CM10?
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
Google's ICS pen APIs automatically enable if a pen driver is enabled in the kernel.
That said, only apps which support the standard pen APIs instead of S-Pen APIs will work.
Examples are Quill and Memo Beta
Entropy512 said:
Google's ICS pen APIs automatically enable if a pen driver is enabled in the kernel.
That said, only apps which support the standard pen APIs instead of S-Pen APIs will work.
Examples are Quill and Memo Beta
Click to expand...
Click to collapse
Thank you so much for your hard work! Looking forward to a stable release for my 8013 .
Entropy512 said:
Google's ICS pen APIs automatically enable if a pen driver is enabled in the kernel.
That said, only apps which support the standard pen APIs instead of S-Pen APIs will work.
Examples are Quill and Memo Beta
Click to expand...
Click to collapse
Does this mean the built in s-pen apps won't work under cm10? Of course that would also mean no split screen I guess. Sorry if these questions seem dense but its all bit confusing.
Sent from my GT-N8013 using Tapatalk 2
Thanks, will give it a try.
espenfjo said:
PREVIEW DISCLAIMER:
This is a PREVIEW : CyanogenMod 10 is nowhere near ready to be used as a daily driver (lots of features still have to be merged), and same is the device support. CHECK THE KNOWN ISSUES LIST BEFORE THINKING ABOUT POSTING.
IF YOU ARE *****ING WITH "When this will be fixed!!!!?????" THEN I'LL JUST CLOSE THE THREAD AND YOU'LL HAVE TO WAIT EVEN MORE.
DISCUSSION THREAD: http://forum.xda-developers.com/showthread.php?p=30744835
IF YOU WANT TO SAY THANKS, HELLO, ASK ABOUT YOUR KERNEL, ISSUES WITHOUT LOG, OR HAVE SEX, THAT'S THE THREAD TO USE!
If you're encountering a bug that isn't listed above, make sure to attach a logcat with your report. If you don't know how to do it, then refrain from posting. Once again, if this thread is becoming a hassle for me, then I'll close it right away. And remember that CM10 IS A WORK IN PROGRESS. No complaints for missing features either.
You can check out #teamhacksung-support on Freenode for live support - but we won't hesitate to ban you if you're *****ing.
Also, a donation on the www.teamhacksung.org webpage is really appreciated. Thanks!
Click to expand...
Click to collapse
Just wanted to point out that most of the replies so far should go in the discussion thread, not this one (this post is off topic too). This thread should be reserved for bug reports with proper logs and other information.
But just to clarify for those new to custom ROMs, CyanogenMod is a ROM that is based off of google's Android Open Source Project. Furthermore, Samsung's stock ROMs include a lot of proprietary parts for which source is not available. Any customizations from Samsung's stock ROMs that aren't in AOSP will never be found in AOSP ROMs (for the most part - I think at one point a talented smali hacker got the Touchwiz camera to work on AOSP ROMs on the Galaxy S).
Thus, specifically for the Galaxy Note 10.1, you will not have the split screen multitasking, floating apps on the navbar, S Note, or any of the other Samsung apps. Most of them have third party equivalents you can find on the market anyway. Split screen multitasking is not something you can really recreate in an app, but there was at one point a project (Onskreen Cornerstone) to build something similar for Android, and Cyanogen at the time expressed interest in including something like it in CyanogenMod. However, that was March of last year and nothing is there yet so who knows if it's still on the table (maybe our friendly neighborhood maintainers can tell us more).
You also won't be able to use any apps that specifically use the S Pen SDK, but apps that use the built in ICS Pen APIs will work (and I don't know why anyone would use the S Pen SDK on ICS, even if there aren't any other active digitizer ICS devices now, there surely will be in the future and limiting yourself to Samsung devices for little benefit seems pointless to me).
Hi @All,
Phonecalls and Textmessage positive too?
ill it run on the 80013?
nightfox11 said:
ill it run on the 80013?
Click to expand...
Click to collapse
Go here
DISCUSSION THREAD: http://forum.xda-developers.com/show...php?p=30744835
nightfox11 said:
ill it run on the 80013?
Click to expand...
Click to collapse
Have you got it running? the thread link doesnt work. I get a status 7 error
Read the OP !!!
Discussion thread link: http://forum.xda-developers.com/showthread.php?t=1854841
nightfox11 said:
ill it run on the 80013?
Click to expand...
Click to collapse
Works for me. It just has a little empty cell signal thing by the clock, but it doesn't seem to have any problems
Sent from my DROID4 using Tapatalk 2
now we have Official Nighties for the 8013 !!! http://get.cm/?device=n8013
I understood that this is the thread to post bugs with logcats in. So here goes.
There is this one network to which I can not connect. It tries and fails. The trying and failing goes on indefinitely. There are other networks to which it connects just fine, but this one keeps failing.
Device: N8010
CM Version: cm-10-20120930-EXPERIMENTAL-n8013-ENTROPY (The first nightly)
Logcat: http://pastebin.com/WaAhji6k
Most notable error from logcat:
E/WifiHW ( 2467): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": No such file or directory
Click to expand...
Click to collapse
It might be a certain security method that is missing, or that the connection socket is somehow closed before it's supposed to.
Router data:
Brand: ZyXEL
model: P-2602HW-D1A
SSID: Smient24Wifi
Security: WPA2-Personal
Encryption: AES
Notes:
- The network used to work fine on stock rom
- it was also broken on build cm-10-20120924-UNOFFICIAL-n8013
- I turned on the logcat, turned on wifi, let it try about 7 times, turned wifi off, turned logcat off.
- The logcat will probably report a poor signal strength. The signal strength is low when it's trying to connect, and jumps to the real value in between connections. This behavior remains exactly the same when I hold my tablet right next to the antenna of the router. I don't know how much this is related to the reported bug.
- Until this bug is fixed, I can work around the issue with connectify, so I won't be whining about when the bug is fixed
Thanks!
This morning's nightly for n8013 bombed, no clue why. If it bombs again I'll look into it further, assuming it was a fluke for now.
Entropy512 said:
This morning's nightly for n8013 bombed, no clue why. If it bombs again I'll look into it further, assuming it was a fluke for now.
Click to expand...
Click to collapse
how did it bomb? as in its not safe to install? or has some issue?
jmwils3 said:
how did it bomb? as in its not safe to install? or has some issue?
Click to expand...
Click to collapse
More a question for the other thread.. but wth.. It didnt build, so the one that "bombed" doesnt exist
Newest nightly from get.cm is safe and ready.
{
"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'm in the Process of Reworking this post, so be warned things will change...
Also, I'm currently in the process of building the newest version of the ROM
Introducing
Project Bland Android, The successor to Bland Android. The goals of Project Bland Android, are simple. To Create three flavors of Android, Original, Cherry, and Dirty Boot (Sadly Name is now Temporarily Final). All work will remain open source, including Dirty Boot. Each Version will always be built upon the latest code base, and always attempt to update quickly. With the goal, of always being open, always being transparent, and always being helpful. This ROM is aimed to be a effort to help the community, and always have the community help others. If your not into that, this ROM will most likely not be for you.
Just like the Previous builds of Bland Android, I am not wanting to work on this all by myself the whole time, so any offers to help will not be turned down, I would love to see this working 100%, and growing, so PM me if interested, or just post in the thread, together, we can grow this ROM from more than a small project, but rather a community effort.
Introducing the Flavors:
Original Flavor, will remain Strictly AOSP, with small amounts of changes.
Cherry will become the Version that develops Somewhat rapidly, every week, there will be a vote for something to be cherry picked into Cherry, then during the next weeks vote, minor builds will be released with the goal of becoming stable by the time the next weeks cherry is integrated.
Finally, Dirty Boot, which will be the flavor that will develop at a slower pace, but with aims of always being stable. Again, code will remain open source, as long as credit is always provided. Not to mention, with enough request, support will be extended to other devices.
-----------------------------------------------------------------------------------------------
Current Android Version: 4.2.1_r1.2
Current Original Flavor: 0.0.3
Download:
-This build is tested to boot, not much more, unclear of bugs, most if not all should work, just supply your own G-APPs.
Current Cherry Flavor: 0.0.0
VOTING CLOSES FOR THIS BUILD: Feb 15th, 2013
Download:
Current Dirty Boot Flavor: 0.0.0
Download:
-----------------------------------------------------------------------------------------------
CREDITS FOR RESOURCES:
Thanks to greenblue for his easy to use source, which can be found here: on his github. or his tutorial:
here..
Kevdliu's Additional Toggles are integrated into the source, which can be found here: in this thread.
What works?
IDK yet
Whats Doesn't work?
IDK yet
Whats weird?
IDK yet
Old Versions...
ROM Build 3 is missing (hoping for a mirror)
ROM Build 2 (Missing Call Audio):
http://www.mediafire.com/download.php?bpib8jovq69xx3m
ROM Build 1 (Missing Audio and G-APPS):
http://www.mediafire.com/download.php?e352ga7jvx2sh4i
does phone volume woirk? does 4g wimax work?
r4dik4l said:
does phone volume woirk? does 4g wimax work?
Click to expand...
Click to collapse
There currently isn't any audio, period, phone volume and music volume aren't working yet though I'm hunting for the reason. And I can't test wimax (not in my area) but I added everything for wimax, so theoretically and I assume it should work.
this is my primary device, so until audio works I will not be able to test it much as soon as volume works I will test 4g wimax
r4dik4l said:
this is my primary device, so until audio works I will not be able to test it much as soon as volume works I will test 4g wimax
Click to expand...
Click to collapse
Well, I'm hunting for a fix for the audio, so hopefully soon that will be fixed.
are you able to use telephony from 4.1.2 or anything like that? I know hp420 has made a rom in the past and there are others, I wish I could help
My build has working audio. Took a while to get to it though since it keeps getting com.android.phone has stopped. Not sure if I should upload it and see if someone can find a fix.
yeah upload it, everyone helping rocks
ubnub82 said:
My build has working audio. Took a while to get to it though since it keeps getting com.android.phone has stopped. Not sure if I should upload it and see if someone can find a fix.
Click to expand...
Click to collapse
in call audio working? because thats the one thats got me stumped, I have everything else working it would appear.
budm said:
in call audio working? because thats the one thats got me stumped, I have everything else working it would appear.
Click to expand...
Click to collapse
Can't test in call audio as the phone force closing stops service.
ubnub82 said:
Can't test in call audio as the phone force closing stops service.
Click to expand...
Click to collapse
It might be worth uploading, seeing if anyone can get it going right.
The GPS is checked as if it is on, but when I try to use Google Now, it cannot register my location. Instead it gives me the option to access settings to turn on Location Services which are already on.
Sent from my Crespo4G using xda app-developers app
The Batman said:
The GPS is checked as if it is on, but when I try to use Google Now, it cannot register my location. Instead it gives me the option to access settings to turn on Location Services which are already on.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
Did you try with Google Maps also? I was able to get a lock in maps, but that was all I tested in. Also, a logcat would be wonderful to see what is going on when this happens for you.
Google Maps attempts to lock into my location, unfortunately, both Google Maps and Google Now don't seem to be able to access GPS.
Going to see if I can get a logcat sometime today. Aldo want to check the settings to see if Google's "Gesture" keyboard is within the rom and if not whether installing a separate apk will work.
Edit: Google's Gesture keyboard is not set by default, however, I was able to install the apk separately and it works great. No logcat yet.
Also, when attempting to look at the Storage section under Settings, it FCs. This is also the case when attempting to access any 4G options for obvious reasons.
Sent from my Crespo4G using xda app-developers app
The Batman said:
Google Maps attempts to lock into my location, unfortunately, both Google Maps and Google Now don't seem to be able to access GPS.
Going to see if I can get a logcat sometime today. Aldo want to check the settings to see if Google's "Gesture" keyboard is within the rom and if not whether installing a separate apk will work.
Edit: Google's Gesture keyboard is not set by default, however, I was able to install the apk separately and it works great. No logcat yet.
Also, when attempting to look at the Storage section under Settings, it FCs. This is also the case when attempting to access any 4G options for obvious reasons.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for the heads up, I will add them to the OP, and please do get the logcat, and if you can get one for when the menus crash also, it might put me in the right direction.
budm said:
Thanks for the heads up, I will add them to the OP, and please do get the logcat, and if you can get one for when the menus crash also, it might put me in the right direction.
Click to expand...
Click to collapse
For some reason, I am unable to get a log cat. I keep getting the message "- waiting for device -" so I'm not exactly sure how to go about obtaining it. (FYI, I'm using a Mac).
If anyone has any tips on how or why this is not working, please feel free to let me know.
Edit: I was able to get the logcat. Do you want me to PM you with it (@budm)?
The Batman said:
For some reason, I am unable to get a log cat. I keep getting the message "- waiting for device -" so I'm not exactly sure how to go about obtaining it. (FYI, I'm using a Mac).
If anyone has any tips on how or why this is not working, please feel free to let me know.
Edit: I was able to get the logcat. Do you want me to PM you with it (@budm)?
Click to expand...
Click to collapse
Thanks for the Logcats, I'll read through them once I've had my morning coffee lol.
EDIT: Boy do I feel stupid. I forgot to include a few things, it should fix most your issues with the Google Now, and Maps.
Awesome. Just let me know if and when you want me to test out the new build. Unless of course you just post it in the OP.
Thanks for getting this rom together btw.
Edit: any way that you could cook the new Gmail apk into the rom? Also, I've been having Superuser issues. The rom doesn't allow for applications to obtain root access.
Sent from my Crespo4G using xda app-developers app
The Batman said:
Awesome. Just let me know if and when you want me to test out the new build. Unless of course you just post it in the OP.
Thanks for getting this rom together btw.
Edit: any way that you could cook the new Gmail apk into the rom? Also, I've been having Superuser issues. The rom doesn't allow for applications to obtain root access.
Sent from my Crespo4G using xda app-developers app
Click to expand...
Click to collapse
I'll be adding it to the OP once I fix/try to fix the settings stuff. and I just added the new Gmail ( I think, I'll double check this though) and I'll provide the SuperUser Zip for any issues. All in all, should be up in about 1 to 4 hours after I finish some things around my house.
is this ROM pretty stable? I am looking forward to flashing this but I know its a pretty new ROM and my phone has been acting funny and dont want to chance screwing it up!!
As the title states every time I get a message through Viber my screen turns on just as if I pressed the power button.
I've tried changing settings and obviously disabled the popup and "unlock for popups" but it still wont stay locked.
Is there something I've missed :s? Is it like that on other peoples Viber? It's damn annoying for me atleast..
Im using a Samsung Galaxy Nexus, maguro. Its been like this on stock 4.0, stock 4.1, a bunch of 4.1 roms and AOKP 4.1.2. Aka its always been like this..
Thank you for your time and please direct me if this is the wrong forums.
ps; ask if you need screen shots or whatnot and I will upload them.
Edit: If I disable notifications for the app through jellybeans new option to disable notifications from the app info screen the screen STILL lights up and unlocks when I get a message..though no notification or anything.
soo no one know anything about it?
Bresch said:
soo no one know anything about it?
Click to expand...
Click to collapse
Do u try change on Viber's setting ?
ok so you will have to gon in viber setting and uncheck new message popup. when you do this , next option unlock for popups , will be automatically disabled
This is something I've explained to viber in detail already and all they told me was to fix the settings so the unlock for pop up is unchecked. I emailed them back stating that it is unchecked and that this issue occurred ever since they did their last update and that I specifically mentioned my settings are set that way in the original email. All I got was an apology and that they would look into it. It's been months since and still no update from them
Sent from my Galaxy Nexus using Tapatalk 2
ljnkshady said:
Do u try change on Viber's setting ?
Click to expand...
Click to collapse
Yes as I explain in the original post I've tried everything.
khuzema9 said:
ok so you will have to gon in viber setting and uncheck new message popup. when you do this , next option unlock for popups , will be automatically disabled
Click to expand...
Click to collapse
Yes I've done that but it still unlocks the screen..
thephantom said:
This is something I've explained to viber in detail already and all they told me was to fix the settings so the unlock for pop up is unchecked. I emailed them back stating that it is unchecked and that this issue occurred ever since they did their last update and that I specifically mentioned my settings are set that way in the original email. All I got was an apology and that they would look into it. It's been months since and still no update from them
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've written to them on twitter but they told me to write them an email but still haven't heard from them..
Also to note: If I disable notifications from the app through the new jellybean app info screen, the screen still unlocks and lits up but no sound or notification..my last desperate attempt would be to disable the permission to unlock screen somehow, is that possible?
Bresch said:
Yes as I explain in the original post I've tried everything.
Yes I've done that but it still unlocks the screen..
I've written to them on twitter but they told me to write them an email but still haven't heard from them..
Also to note: If I disable notifications from the app through the new jellybean app info screen, the screen still unlocks and lits up but no sound or notification..my last desperate attempt would be to disable the permission to unlock screen somehow, is that possible?
Click to expand...
Click to collapse
dude just try reinstalling it then and are you using any custom rom . though it should not cause such a problem
khuzema9 said:
dude just try reinstalling it then and are you using any custom rom . though it should not cause such a problem
Click to expand...
Click to collapse
As I stated in the original post, tried multiple times. Even went back to stock ICS just to see if it would help.
I believe it's the latest update they did last October which causes this issue. Gives me the same result in both my gnex and nexus one. Prior to the update it wasn't acting like it. I made a follow up email and the response I got was that it has been forwarded to the 'proper department'
Sent from my Galaxy Nexus using Tapatalk 2
thephantom said:
I believe it's the latest update they did last October which causes this issue. Gives me the same result in both my gnex and nexus one. Prior to the update it wasn't acting like it. I made a follow up email and the response I got was that it has been forwarded to the 'proper department'
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I had the problem before that and during some version it stopped and came back in October sometime sounds about right. It's a shame really.. But it's a free app that originated from iOS so shouldn't expect too much I guess..
Is there any way to strip the app of the permission?
I think going back to the previous version would fix it. But the one prior to the current version had proximity sensor issues
Sent from my Nexus 4 using Tapatalk 2
Hi,
This is a member of the Viber R&D Team.
@Bresch - Thanks for reporting your issue...
We are continuously working on updates, we hope the next update will fix this issue too.
One question, can you please tell us if this issue is unique only to Viber or is it relevant to other apps too?
Thanks,
Viber
Viber Team said:
Hi,
This is a member of the Viber R&D Team.
@Bresch - Thanks for reporting your issue...
We are continuously working on updates, we hope the next update will fix this issue too.
One question, can you please tell us if this issue is unique only to Viber or is it relevant to other apps too?
Thanks,
Viber
Click to expand...
Click to collapse
It is unique to viber. I've never had anything else unlock the screen...Especially not when you have the screen locked with a code or password.
Thanks for the info.
As we said, when our next major update is released, please try it out and let us know if the problem is resolved. If not, we'll be right here to assist and check the matter thoroughly.
Tested the update and still screen unlocks despite being unchecked in the settings. Nice work on being able to use system notifications though
Sent from my Nexus 4 using Tapatalk 2
Hi there,
As some of you have already noticed, we have released a new version of Viber - 2.3.0 !
What's new?
- Use your own ringtones from Android as your Viber ringtones!
- Include cool emoticons in your Viber text message.
- Reply to cellular (regular) SMS using Viber.
- Share Stickers with your Viber contacts.
- Add a custom location to your Viber texts.
- Many other enchancements and improvements.
So, make sure you download the latest version!
Please feel free to let us know your thoughts, questions and comments, we'd be happy to hear from you.
Viber Team
@thephantom -
Thanks for the report.
We kindly ask that you take a minute and report the details of the problem to our support team using this direct link: http://bit.ly/ukGVJ0
With this information, our development team will hopefully be able to find the source of the problem, and ultimately resolve it
Thanks in advance
Thanks for responding Viber team. I have already sent a report since Oct 4 which unfortunately doesn't have any concrete response. In fact, here's a screenshot of it tagged closed.
{
"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"
}
It would be nice to look at it as I've explained before that not only did I experience it on jellybean but also on another phone running gingerbread
Sent from my Nexus 4 using Tapatalk 2
@thephantom -
Thank you for the info.
There might have been some confusion there - "Closed" doesn't mean we stopped handling the problem, it merely means that it has been transferred departments within our own company.
However, I will make sure that this issue is brought up in our upcoming meetings and we will see what can be done to reproduce it here in our labs.
We apologize for any inconvenience caused.
Wow. Gotta hand it to you. After posting in a public forum, I got an email update all of a sudden. Whereas before, it took weeks and even months for a response. I guess it's better to post issues here
Sent from my Nexus 7 using Tapatalk 2
what's the point with having the permission to unlock screen anyway? its totally unnecessary! Why would you EVER want your phone waking up?
If its in your hand, you just unlock it yourself.
If its in your pocked, you NEVER want it to unlock.
Simply just strip the app of the permission please..this is not iOS. We don't want our phones getting lit up..
{
"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"
}
Android 4.1.2
ParanoidAndroid 2.56
Source compiled
You can follow the PA-JB Progress for Galaxy Nexus in this thread: http://forum.xda-developers.com/showthread.php?t=1619582
Follow Paranoid Android officially on:
Facebook : https://www.facebook.com/paranoidgoogle
Twitter : https://twitter.com/paranoid_team
G+ : http://goo.gl/e3tKJ
LTE Prolog
This is not a typical port! It was compiled from source with MadMack's sources specifically for our LTE devices!
That being said, I do not own or take credit for Paranoid Android.
Please be sure to read this entire post and please refrain from asking any questions that have been answered here!
Orginal Thread Here: http://forum.xda-developers.com/showthread.php?t=2069430
Please feel free to browse and search for questions that may have been answered already!
Warning: CM10 don't support ntfs/exfat
There is no ntfs/exfat externel sdcard support in cm10. To use ext sdcard you will need to reformat it to fat32 using third party utilities in windows. If you already flashed you can use adb in cwm recovery to pull your data.
Latest build
$ pa_i317_Skyy_V2.56.zip
> Download link: http://d-h.st/hCZ
When updating always make a copy of your /etc/paranoid/properties.conf before flashing, just in case. If restore dont work push this after flashing, restore permission and reboot.
Gapps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
AOSP alternatives to touchwiz apps
Githubs:
https://github.com/Utacka
https://github.com/ParanoidAndroid
https://github.com/CyanogenMod
CM gerrit
PA gerrit
Special thanks to
Madmack for your sources and answering my dumb questions!
Slick_Rick for everything you helped me with
ManelScout4Life for pointing me in the direction of building from source!
Utacka!
the entire PARANOIDANDROID team
CYANOGENMOD team
imilka
Find any combination you like, scale and project apps, widgets and system components!
PER-APP-COLOR, Paranoidandroids newest invention. Define apps in your regular hybrid panel (same that allows you to scale apps individually and choose their interface). See your phone fade into the color definition of your current app, press home or go elsewhere and it fades back. Create as many combinations you like, you can even dabble with opacity. This feature is made possible by our hybrid engine, which is unique to this rom.
To be honest, this is not tablet mode at all, it has nothing to do with silly build.prop hacks. This is the first and only Android rom to feature true Hybrid mode. This rom lets you scale and project every app, every widget, even systemcomponents individually. Remember, android is modular, everything is an app: Lockscreen, navigationbar, dialogs, popups, keyboards, widgets, and your regular apps of course. Apps have the capability to switch into various designs or layouts according to the device they run on. This can result in a complete new experience as many apps will transform to the better.
Now for every element that you like chose a mode (PhoneUI, Phablet/Nexus-7UI, TabletUI) and/or a size. You are 100% independent of the system DPI which runs nicely in whatever value it has been assigned to. You do not need to boot your phone into a certain DPI. Neither will most of the changes you apply require a reboot. You will not suffer from the myriads of troubles which normally haunt you under build.prop tablet mode. Your market, phone, etc. will all work, apps won't shrink on you unless you shrink them yourself. This project will entirely transform your device, but retain the aesthetics and the feel of your phone.
Donations to molesarecoming
to D4rKn3sSyS
to Cyanogenmod
CWM: YOU NEED TO FULLWIPE IF YOU ARE COMING FROM ANOTHER ROM
CWM: Install Zip: Rom: http://d-h.st/hCZ
CWM: Install Zip: Gapps: http://goo.im/gapps/ (latest gapps-jb and even when updating to new PA build)
Reboot and edit your Apps Dpi & Layout under Settings/Paranoid Settings - DO NOT RESTORE YOUR OLD PROPERTIES FOR NOW
If you want to explore the various phone modes, tap "Configuration," chose an option, wait for it to finish, then do a manual reboot
Video tutorial: http://www.youtube.com/watch?v=72Ow-YQeex4
pa webpage: http://www.paranoid-rom.com/
You want to port PA? Take a look here: http://forum.xda-developers.com/showthread.php?p=27558806
Go to Settings, System, Font size, set it to NORMAL
Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen
Trebuchet Settings: margins:SMALL, show permanent searchbar:YES, Grid: 4x4, resize all widgets:YES, Wallpaper scrolling: OFF
Paranoid Android Wallpapers: HERE
If you have an issue and you want to call our attention, here's what you do:
1. Try everything you can, find solutions for yourself. Wipe caches, revert all your settings you have made, go back to your stock Kernel, factory reset if you have to or reflash the rom. Assume that the issue is on your side and try your best to isolate it.
2. Search this thread and Cyanogenmods aswell (its our base) for possible reoccurences of your issue and hopefully solutions that may have come up.
3. If you think the issue is important enough that we should cease our work and look into it, post your issue, BUT ...
... stay friendly, do not demand anything, do not threaten
... explain your issue as precise as you can, name the exact apps and conditions that cause trouble, help us to replicate the issue right away. If we can't there's no way we can fix it and your post will simply clutter the thread
... collect evidence, keep in mind this is a developer thread so even if you are not one, do us the favor and research how to record logcat. logcat is the single most important help you can give us to resolve your issue.
Paranoid Android Devs
Cyanogenmod Team
imilka for the initial upbringing
You can find the device source and kernel source at the CyanogenMod Github
Official GT-N7100 rom
If you appreciate this download please press the Thanks Butto
How to set the workspace mode
How to change an apps Layout and size
http://paranoid-rom.com/forum/changelogs-news
reserved
First!! Yay! Great gonna check this out!
Sent from my SGH-T889 using Tapatalk 2
Is this any different than the version submitted in the ORIGINAL Android development forum here:
http://forum.xda-developers.com/showthread.php?t=2075894
Gack69 said:
Is this any different than the version submitted in the ORIGINAL Android development forum here:
http://forum.xda-developers.com/showthread.php?t=2075894
Click to expand...
Click to collapse
I can't really say. I compiled this myself on the ATT forums and was suggested to post it here as it works on all LTE devices...I guess I missed that there was a thread in original development =x
Are you gonna be able to steadily update this? Or keep up with it?
Sent from my SGH-T889 using xda app-developers app
heroskyy said:
I can't really say. I compiled this myself on the ATT forums and was suggested to post it here as it works on all LTE devices...I guess I missed that there was a thread in original development =x
Click to expand...
Click to collapse
If this is actually source compiled, that is the difference. The other one says so in the OP but further along he states it is a port and not compiled. As such, the threads are both in the wrong sections. This is original (you made it), his is not (he copied/pasted it).
yungtexas said:
Are you gonna be able to steadily update this? Or keep up with it?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
indeed!
daveid said:
If this is actually source compiled, that is the difference. The other one says so in the OP but further along he states it is a port and not compiled. As such, the threads are both in the wrong sections. This is original (you made it), his is not (he copied/pasted it).
Click to expand...
Click to collapse
Ahhh well fair enough then.
Also, Im going to include a link to my ATT thread that may answer any questions some of you may have.
The OP is properly Paranoid formatted. So I am behind this
If I may make a suggestion though? It was quite the scroll with those pictures. It would be nice if you would hide the some of them with the
tags.
For example,
Here is a paragraph! :victory::angel::crying:
And it would be easier on mobile connections and slow internet in general.
Thank you! And great work! Let me know if you need a server mirror!
heroskyy said:
indeed!
Ahhh well fair enough then.
Also, Im going to include a link to my ATT thread that may answer any questions some of you may have.
Click to expand...
Click to collapse
You got my vote boss... Imma download this and give it a try! Thanks again.... I loved this on my htc one s... Back at it haha
Sent from my SGH-T889 using xda app-developers app
Yeah it seems like this rom is the one that should be in the "original" section?
Sent from my GT-N7105 using xda app-developers app
does this one have working sliders in PA settings? the one in the original section doesn't.
Sent from my SGH-T889 using xda app developers app
darkierawr said:
The OP is properly Paranoid formatted. So I am behind this
If I may make a suggestion though? It was quite the scroll with those pictures. It would be nice if you would hide the some of them with the
tags.
For example,
Here is a paragraph! :victory::angel::crying:
And it would be easier on mobile connections and slow internet in general.
Thank you! And great work! Let me know if you need a server mirror!
Click to expand...
Click to collapse
For sure! I'll do that when I get home.
HandsomeAssDomo said:
does this one have working sliders in PA settings? the one in the original section doesn't.
Sent from my SGH-T889 using xda app developers app
Click to expand...
Click to collapse
Yup! Everything works. The only problems you'll find are common aosp problems. Some users may experience Bluetooth problems...but others will not. Its an odd problem that we're working on.
heroskyy said:
For sure! I'll do that when I get home.
Yup! Everything works. The only problems you'll find are common aosp problems. Some users may experience Bluetooth problems...but others will not. Its an odd problem that we're working on.
Click to expand...
Click to collapse
Damn... this is the post i was looking for.. i want a PA build so bad but i cant give up bluetooth.. might have to try it anyway and report back.. i ran the beer rom for a minute and there was no BT there either.
HandsomeAssDomo said:
does this one have working sliders in PA settings? the one in the original section doesn't.
Sent from my SGH-T889 using xda app developers app
Click to expand...
Click to collapse
I dont think anyone really understand the concept of 2 dev sections and I personally think its inane and confusing
Is anyone having the problem of the signal bouncing back and forth from 3g to h? Im using t mobile version of the phone. I wiped everything by the way.
Sent from my SGH-T889 using xda app-developers app
wellingtonarmelin said:
Is anyone having the problem of the signal bouncing back and forth from 3g to h? Im using t mobile version of the phone. I wiped everything by the way.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Lol
Sent from my SGH-T889 using xda premium
calls are choppy. any suggestions on how to fix this?
Thank you
{
"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"
}
PAC-ROM is built with our own tweaks and options, including picks and features from the best ROMs out there!
Why choose among ROMs, when you have All-in-One !!
* By flashing this, you automatically void your warranty! *
* If your phone breaks, blows up or runs away from you, do not cry to us! *
* Do not ask for ETAs!! *
* Download the ROM and GApps *
* Reboot to recovery *
* Wipe data/factory reset *
* Flash the ROM and then GApps *
* Reboot your phone *
* Enjoy *
* Download the latest version *
* Reboot to recovery *
* Flash the ROM *
* Wipe both dalvik cache and cache *
* Reboot your phone *
* Enjoy the latest version of PAC-ROM *
* Submit a bug report *
* Submit a patch *
* None for now *
* PAC-ROM Downloads *
* GApps *
* PAC-ROM Team *
* Cyanogen Team *
* AOKP Team *
* DirtyUnicorns *
* SlimRoms *
* Vanir *
* Omnirom *
* Special thanks to all our Build Bot Providers (see Contributors list for all names) *
* PAC Graphix Team - Graphics, logos and images (see Contributors list for all names) *
* And of course, thank you for your love and support! *
Support us with these banners:
Help with server costs
PAC-man ROM for the LG Optimus G - Devices and threads:
Sprint ls970/geespr: Here
Canadian e973/geeb: [ROM][OFFICIAL][KitKat 4.4.4][E973-GEEB] PAC-man 4.4.4.RC-2
International e975/gee: [ROM][OFFICIAL][KitKat 4.4.4][E975-GEE] PAC-man 4.4.4.RC-2
Thanks a bunch!
I'm a bit confused.
The download link you provided takes me to PacMan files basketball files>LS970
I do not see this particular build (PAC-man 4.4.4.RC-1) in any of this folders.
However I do see a similar build label in the p970 folder (release).
Help me sort this out.
mesacarvin said:
Thanks a bunch!
I'm a bit confused.
The download link you provided takes me to PacMan files basketball files>LS970
I do not see this particular build (PAC-man 4.4.4.RC-1) in any of this folders.
However I do see a similar build label in the p970 folder (release).
Help me sort this out.
Click to expand...
Click to collapse
Yeah, sorry about that. I'm still in the process of taking over as this device's maintainer. Once I'm done, the ls970 will be added back as a supported device and you should expect to see fresh nightlies rolling out soon.
I'm happy to say that I'll be your new maintainer. The ls970 is once more a supported device and as such, will be getting nightlies rolled out soon. I'll be around for you guys if you need help or have questions. Looking forward to getting this stale August 24th build off my device, and I know you guys are too.
Welcome and thanks for taking this awesome ROM to maintain it. :good:
As you are the maintainer now, I'll suppose that is fine tho post feedback about the ROM to you...
I've been running that last old build (08/24) since a few weeks. only two things to report:
1- having delay waking up the device when it self goes off due the ''screen off time'' but not if I lock it through the button.
2- bsod sometimes, with the built in kernel and with different custom kernels too, that's why I'm guessing is ROM related.
FcoEnrique said:
I've been running that last old build (08/24) since a few weeks. only two things to report:
1- having delay waking up the device when it self goes off due the ''screen off time'' but not if I lock it through the button.
2- bsod sometimes, with the built in kernel and with different custom kernels too, that's why I'm guessing is ROM related.
Click to expand...
Click to collapse
1) I can confirm this problem. It cropped up in the last couple builds. It may be temporary, so let's wait and see if it occurs in the latest nightlies once they roll out.
2) BSOD as in a blue screen saying something like "subsystem crash"? I've gotten those a few times too. They're just the weirdest things to see on an Android system. And they occur for me at the oddest times, like when the phone's just sitting there doing nothing. I haven't gotten any lately though. This is another case of waiting and seeing if the problem has been fixed in the latest nightlies.
As for the nightlies, you can see here that I've added the ls970 back into nightly.xml, so our Jenkins build bots will be getting around to making a build for the device soon. By the way, if you'd like to volunteer one or more of your machines as a build bot and help speed up our nightly build process, by all means view this thread. Thanks.
rectec said:
1) I can confirm this problem. It cropped up in the last couple builds. It may be temporary, so let's wait and see if it occurs in the latest nightlies once they roll out.
2) BSOD as in a blue screen saying something like "subsystem crash"? I've gotten those a few times too. They're just the weirdest things to see on an Android system. And they occur for me at the oddest times, like when the phone's just sitting there doing nothing. I haven't gotten any lately though. This is another case of waiting and seeing if the problem has been fixed in the latest nightlies.
As for the nightlies, you can see here that I've added the ls970 back into nightly.xml, so our Jenkins build bots will be getting around to making a build for the device soon. By the way, if you'd like to volunteer one or more of your machines as a build bot and help speed up our nightly build process, by all means view this thread. Thanks.
Click to expand...
Click to collapse
Happy to know that our device is back in business.
By bosd or "black screen of death", I mean that when I try to unlock/wake up the device it doesn't, keys lights up but the screen stays off.
I'll would love to help with the building process, I even would love tho be able to build some ROMs but my machine doesn't have the requirements :/
FcoEnrique said:
Happy to know that our device is back in business.
Click to expand...
Click to collapse
You and me both
FcoEnrique said:
By bosd or "black screen of death", I mean that when I try to unlock/wake up the device it doesn't, keys lights up but the screen stays off.
Click to expand...
Click to collapse
Oh. Yeah I've had that problem too. It's a pain in the ass but at least you can hold the power button down for a little bit to hard restart the phone. But we'll have to see if we have this problem with the latest nightlies as well, because it may have already been fixed.
FcoEnrique said:
I'll would love to help with the building process, I even would love tho be able to build some ROMs but my machine doesn't have the requirements :/
Click to expand...
Click to collapse
No problem. They're pretty demanding requirements and rightfully so; building a single nightly can take hours. That was just a general solicitation in case anyone who can meet the requirements happens to stumble upon my post. But if you want to contribute a build bot, next time you're in the market for PC hardware, I'd recommend getting one of those cheap AMD 8 core CPUs, since building is a heavily multi-threaded process. Thanks for your interest
Some goodies in the last build like stop and resume downloads, good to have new builds again. :good:
so far the only bug in my end is still present, having that delay when unlocking after it self turn off the screen.
Edit: I think that I've found another one,something wrong with YouTube.
FcoEnrique said:
Some goodies in the last build like stop and resume downloads, good to have new builds again. :good:
so far the only bug in my end is still present, having that delay when unlocking after it self turn off the screen.
Edit: I think that I've found another one,something wrong with YouTube.
Click to expand...
Click to collapse
Yeah I still have the delay too, even though I started with a fresh install and just restored my apps with Titanium. I'm going to test these bugs on a true fresh install, and if they're there I'll ask around about it.
Edit: Yep. Just as I thought, the (or at least a) cause of the screen on delay is from disabling the lockscreen from quick settings. As soon as I re-enable the lockscreen, the delay goes away for me. Can you confirm that this happens with your phone too? I've attached a couple images of my quick settings to illustrate what I mean.
As for the YouTube problem, before I've noticed occasional artifacting/video corruption all over videos, which goes away when I fiddle with the seekbar. With the latest gapps' YouTube I just see a small band of artifacting at the bottom of the screen that won't go away. When I update to the latest YouTube through the Play Store, I see the same all-over artifacting that I saw before (https://puu.sh/bHxBq/a65975f799.png), only it doesn't go away. I don't see anyone complaining about it on the Play Store entry, so I'll assume it's specific to us.
I'll ask around about these problems. For now I'll note them in the "Other info" section of the OP. I'll keep you guys informed.
rectec said:
Yeah I still have the delay too, even though I started with a fresh install and just restored my apps with Titanium. I'm going to test these bugs on a true fresh install, and if they're there I'll ask around about it.
Edit: Yep. Just as I thought, the (or at least a) cause of the screen on delay is from disabling the lockscreen from quick settings. As soon as I re-enable the lockscreen, the delay goes away for me. Can you confirm that this happens with your phone too? I've attached a couple images of my quick settings to illustrate what I mean.
As for the YouTube problem, before I've noticed occasional artifacting/video corruption all over videos, which goes away when I fiddle with the seekbar. With the latest gapps' YouTube I just see a small band of artifacting at the bottom of the screen that won't go away. When I update to the latest YouTube through the Play Store, I see the same all-over artifacting that I saw before (https://puu.sh/bHxBq/a65975f799.png), only it doesn't go away. I don't see anyone complaining about it on the Play Store entry, so I'll assume it's specific to us.
I'll ask around about these problems. For now I'll note them in the "Other info" section of the OP. I'll keep you guys informed.
Click to expand...
Click to collapse
Yes that's exactly what is going on with youtube.
about enabling/disabling lockscreen in quick settings, I'll check that, as I dont have that toogle added to my QS screen.
I'll let you know if that solves it.
EDIT:
Nope that's not the problem, I have it enabled.
Hey guys. Anyone else having issues with NFC? I'm running on the 9/20 nightly and I can't get it to come one. I check the NFC box and it just fades but it won't come on.
Sent from my LG-LS970 using XDA Free mobile app
ibleo02 said:
Hey guys. Anyone else having issues with NFC? I'm running on the 9/20 nightly and I can't get it to come one. I check the NFC box and it just fades but it won't come on.
View attachment 2946904
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
yup, happened to me, but after a reboot it works.
the annoying bug that is still present for me is the delay when waking up the device...
i think I'll try another ROM to see if it's only PAC.
Sorry for the delay. XDA decided to not email me about thread replies.
So I've been told the delay is normal behavior when you've disabled the lockscreen through quick settings, since it's bypassing the lockscreen. I wish I could give you a better explanation. It's not bug, just an unintended side effect. Hopefully we'll implement a better method in the future that doesn't have a delay.
Since you still have the delay even when the lockscreen isn't disabled, I'd do a nandroid backup, wipe, then do a fresh install of the ROM. Then see if the issue appears. If it doesn't, then it could be something wrong your current install. If it does still appear, then I don't know what to tell you lol. All I can say is that I only have a screen on delay when I have the lockscreen disabled - both in a fresh install and a non-fresh install - and that it's apparently normal behavior.
As for the YouTube corruption, I'm not having that problem on my current install. I'd like to see if more people have this problem before we go on a full on investigation.
rectec said:
Sorry for the delay. XDA decided to not email me about thread replies.
So I've been told the delay is normal behavior when you've disabled the lockscreen through quick settings, since it's bypassing the lockscreen. I wish I could give you a better explanation. It's not bug, just an unintended side effect. Hopefully we'll implement a better method in the future that doesn't have a delay.
Since you still have the delay even when the lockscreen isn't disabled, I'd do a nandroid backup, wipe, then do a fresh install of the ROM. Then see if the issue appears. If it doesn't, then it could be something wrong your current install. If it does still appear, then I don't know what to tell you lol. All I can say is that I only have a screen on delay when I have the lockscreen disabled - both in a fresh install and a non-fresh install - and that it's apparently normal behavior.
As for the YouTube corruption, I'm not having that problem on my current install. I'd like to see if more people have this problem before we go on a full on investigation.
Click to expand...
Click to collapse
Ups I forgot to try youtube in the last build...
as for the delay, well, I don't know what it could be, I wiped my phone completely even sd card (for accident ) and the delay persist
FcoEnrique said:
Ups I forgot to try youtube in the last build...
as for the delay, well, I don't know what it could be, I wiped my phone completely even sd card (for accident ) and the delay persist
Click to expand...
Click to collapse
I'm guessing it doesn't occur in other ROMs?
rectec said:
I'm guessing it doesn't occur in other ROMs?
Click to expand...
Click to collapse
Nope, I'm in AOKP right now and it doesn't happens, neither in Carbon before PAC.
FcoEnrique said:
Nope, I'm in AOKP right now and it doesn't happens, neither in Carbon before PAC.
Click to expand...
Click to collapse
Out of curiosity, do you guys happen to be using see-through on the lockscreen. I know that creates major delays for me when turning the screen on
goldflame09 said:
Out of curiosity, do you guys happen to be using see-through on the lockscreen. I know that creates major delays for me when turning the screen on
Click to expand...
Click to collapse
Nope... even after a clean flash.
it happens to me right away :/