Right guys you know whats coming.....
{
"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"
}
P A C man ALL IN 1
Check the Q&A Thread for PAC-specific questions!
ROM INTEL
Here we go then, This is the PAC-man AIO (All-in-one) ROM, for the Xperia TX. Since the TX isnt that different from the T, I compiled it, asked a tester to test it, and here it is! A big shoutout to @Rycon33 who did some extensive testing on the ROM for me.
I'm searching two more testers to test updates before releasing it into the wild. If you want to do so, please shoot me a PM
These testers will get the ROM, they will test it, and after the release to the public will take place.
PAC is a combination of the three biggest ROMs here at XDA. Paranoid Android, Android Open Kang Project and CyanogenMod. It features CM profiles, PA's Hybrid Engine, and ROM Control by AOKP. Everything!
A main complaint under the developers whom originally developed their features about 'mashup' ROMs, is that they are messy, and the different features aren't integrated as well as the individual projects. PAC was the first of all 'mashup' ROMs and has the best integration of them all. It took a LOT of work of thinking behind to merge the frameworks in the right order. These are not just your daily git cherry-pick developers trying to pull money off of XDA
PAC-man has a solid team with good developers and device maintainers, bringing you this totally awesome ROM. :victory:
If you'd like to support me or the PAC developers, be sure to drop them a thanks / beer!
FEATURES
Hybrid Framework
CM10.1
AOKP
AOSPA
Per App DPI
Per App Color
Pie Controls
Open Source Camera HAL
cLock
Hardware Key Control
Any Widget on lockscreen
CM Profiles
Lock Screen Shortcuts
Lock Screen ring target
Fresh compiled CM10.1 kernel
Init.d Support
...
...
...
The list is endless.
BUGS
Basically every bug from CM10.1/FXP
Headphones
Vibration
Camera is a bit buggy sometimes
You tell me... Read down here how to report bugs, which are really usefull to me.
REPORTING BUGS
Source: JellyTime
Code:
How To File a Bug Report with Logcat:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb logcat' without the quotes
[*] Start the app that causes the issues
[*] Wait for the app to close or get to the error
[*] Copy logcat contents and put in pastebin
[*] Copy pastebin links here
[/LIST]
How To Find Wakelocks:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb shell cat /proc/wakelocks > wakelocks.txt' without the quotes
[*] Copy contents and put in pastebin
[*] Copy pastebin links on your post
[/LIST]
How To Get dmesg logs:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb shell dmesg > dmesg.txt' without the quotes
[*] Copy contents and put in pastebin
[*] Copy pastebin links on your post
[/LIST]
Before filing a bug report, please consider the answer to these:
[LIST]
[*] Is the bug reproducible?
[*] How do you reproduce it?
[*] What is the expected behavior?
[*] What actually happens?
[*] Are you on the default Kernel?
[*] Did you restore data of System Apps using Titanium Backup?
[/LIST]
CHANGELOG
Go and check out PAC on github
INSTALLATION / NOOB GUIDE
Unlock your bootloader, if you haven't done so.
Download this the latest version of this badboy!
Grab a copy of the latest GAPPS package
If you come from a stock rom, reboot to bootloader, flash the boot.img from the ROM zip.
Reboot to recovery
Do a "Factory Reset" if coming from any other ROM than the semi-latest version of PAC
Flash the ROM! /system will be automatically wiped during install, as in all good ROMs.
Flash GAPPS
Reboot
Enjoy!
DOWNLOADS
Please be aware that the ROM is throughly tested, but that there are certain bugs!
Grab the latest PAC-man HERE or HERE
Normal GAPPS
Inverted GAPPS
DAILIES
Since shortly, Hayabusa builds are also available on PAC's basketbuild, check it out here: http://pacman.basketbuild.com/index.php?dir=main/hayabusa/nightly/
FAQ
Q: My sound is way too low!
A: Find Pimp My Rom in the Play Store, and install xLoud with it. This can also bring back BE with unlocked bootloaders!
Q: Paranoid Android preferences do not work!
A: https://github.com/ParanoidAndroid/android_vendor_pa/commit/e99a9b192386ca186dfe5a52126ce6fbe7da79a5 - or grab one of the latest ParanoidAndroid ROMs and sideload /system/app/paranoidpreferences.apk
SIGPIC
Code:
http://i.imgur.com/MOG8AGD.png
Fan-art is always welcome
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
a BIG thanks to these people:
szl.kiev and PACman Team
CM team
ParanoidAndroid team
AOKP Team
XDA for just about everything else
@Rycon33 for testing this release
If you think you need to be thanked, just let me know
thanks to techfanatic9 for this.....
so excited to see PACman on TX
thousands of thanks :good::good::good:
Awesome mate, many TX users will surely be happy.
Though still many things to iron-out(see the mentioned bugs and some you need to tell the dev), people will still be quite satisfied with the ROM as I did.
I just want to reiterate that during testing I didn't check if the voice calls are fine(lol it should be the basic thing to test).
Though I think even at this early stage, it's good that everyone gets to test it and it will definitely help the dev more because more feedbacks are going to flow.
So fellow TX users, flash it and give feedback.
Tapatalked from my bricked TX
Rycon33 said:
Awesome mate, many TX users will surely be happy.
Though still many things to iron-out(see the mentioned bugs and some you need to tell the dev), people will still be quite satisfied with the ROM as I did.
I just want to reiterate that during testing I didn't check if the voice calls are fine(lol it should be the basic thing to test).
Though I think even at this early stage, it's good that everyone gets to test it and it will definitely help the dev more because more feedbacks are going to flow.
So fellow TX users, flash it and give feedback.
Tapatalked from my bricked TX
Click to expand...
Click to collapse
I've been running it for the past few hours and everything seems alright.
The headphones don't seem to register but calls do work and everything else seems to be fine.
Keep up the great work, glad to see support for the TX as well.
Daily builds are a fact!
Bluetooth is kinda spotty so I can't accurately say if it works. It worked for a little bit with my radio but then it stopped working and hasn't worked since.
There's also a reboot whenever it tries to install something over 5mb's sometimes. I'm not entirely sure why but it happens whenever it feels like it.
Vibration does not work (already been listed) and the battery is draining kinda fast. Not entirely sure as I haven't fully cycled it but it has been kinda grr from what I've seen.
Also the touch screen calibration seems to be a tad bit off. I often find myself pressing something else when I directly press what I intended. Its not bad to the breaking point but sometimes I have to take a moment to think about what I'm actually pressing.
Now this looks interesting
Will give this a try once i backup all my stuff
UPDATE : my stock rom was rooted, but bootloader was still locked. so i got my bootloader unlocked, and flashed the pacman's boot.img. after booting into CWM, it says that "E: Unable to mount/data" Tried to format /data , /cache, /system , /dalvik-cache, all the same.
Tried TWRP, but also no bueno. Display was cut into half, and also got the same error as CWM. And due to that, I kept getting bootloops
ericmaxman said:
Now this looks interesting
Will give this a try once i backup all my stuff
UPDATE : my stock rom was rooted, but bootloader was still locked. so i got my bootloader unlocked, and flashed the pacman's boot.img. after booting into CWM, it says that "E: Unable to mount/data" Tried to format /data , /cache, /system , /dalvik-cache, all the same.
Tried TWRP, but also no bueno. Display was cut into half, and also got the same error as CWM. And due to that, I kept getting bootloops
Click to expand...
Click to collapse
try to flash it using other kernel including CWM(6.0.X.X )
Good news guys, I've been testing the latest build(2-June) and some issues has been fixed, e.g. still no random reboots here, creating lockscreen shortcuts is Ok now, and many more.
Though some minor issues is still there like no vibration and headset/earphone not detected.
But overall, ROM is really very fluid and smooth. Plus we can use those awesome themes available around. Check out those new themes like flatron theme and simplex theme. They are simply awesome.
EDIT: and we can enter recovery now(from OFF state) by pressing volume button. last time we can go recovery only when we're coming from OS.
Tapatalked from my PACmanned TX
Leo said:
try to flash it using other kernel including CWM(6.0.X.X )
then shutdown and flash the pac boot.img in fastboot mode
Click to expand...
Click to collapse
Thanks for the heads up. I'll give it another try
Rycon33 said:
Good news guys, I've been testing the latest build(2-June) and some issues has been fixed, e.g. still no random reboots here, creating lockscreen shortcuts is Ok now, and many more.
Though some minor issues is still there like no vibration and headset/earphone not detected.
But overall, ROM is really very fluid and smooth. Plus we can use those awesome themes available around. Check out those new themes like flatron theme and simplex theme. They are simply awesome.
EDIT: and we can enter recovery now(from OFF state) by pressing volume button. last time we can go recovery only when we're coming from OS.
Tapatalked from my PACmanned TX
Click to expand...
Click to collapse
Glad to hear that the ROM is improving :good:
Any other bugs that we need to take note of?
PAC 22.4 is here!
djpbx said:
PAC 22.4 is here!
Click to expand...
Click to collapse
Does it fix the headphone bug?
Fuzalert2k said:
Does it fix the headphone bug?
Click to expand...
Click to collapse
Unfortunately, not yet, same as in CM.
Tapatalked from my bricked TX
v23 is up
Any bug solved?
Vibration is very important for me
where can i find the changelog in github....
Leo said:
where can i find the changelog in github....
Click to expand...
Click to collapse
the normal commits of PAC are actually the changelog. you can also visit settings -> about phone -> changelog on your android itself.
navigation bar isnt showing
Just installed the rom and works fine but my navigation bar isnt showing.. can somebody help me with this?
boydje said:
Just installed the rom and works fine but my navigation bar isnt showing.. can somebody help me with this?
Click to expand...
Click to collapse
try to add this line in build.prop(make a backup is suggested)
qemu.hw.mainkeys=0
Click to expand...
Click to collapse
Related
{
"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"
}
thanks to techfanatic9 for this.....
Right guys you know whats coming.....
P A C man ALL IN 1
Check the Q&A Thread for PAC-specific questions!
ROM INTEL
Here we go then, I've taken the stick in the PAC-man relay race from @[vertigo] to make sure this ROM does not die. Our Xperia T has been added to the PAC sources, and has been built from that. I'm acknowledged as official maintainer by the PAC team, and therefore this is an official release
PAC is a combination of the three biggest ROMs here at XDA. Paranoid Android, Android Open Kang Project and CyanogenMod. It features CM profiles, PA's Hybrid Engine, and ROM Control by AOKP. Everything!
A main complaint under the developers whom originally developed their features about 'mashup' ROMs, is that they are messy, and the different features aren't integrated as well as the individual projects. PAC was the first of all 'mashup' ROMs and has the best integration of them all. It took a LOT of work of thinking behind to merge the frameworks in the right order. These are not just your daily git cherry-pick developers trying to pull money off of XDA
PAC-man has a solid team with good developers and device maintainers, bringing you this totally awesome ROM. :victory:
If you'd like to support me or the PAC developers, be sure to drop them a thanks / beer!
FEATURES
Hybrid Framework
CM10.1
AOKP
AOSPA
Per App DPI
Per App Color
Pie Controls
Open Source Camera HAL
cLock
Hardware Key Control
Any Widget on lockscreen
CM Profiles
Lock Screen Shortcuts
Lock Screen ring target
Fresh compiled CM10.1 kernel
Init.d Support
...
...
...
The list is endless.
BUGS
All FXP CM10.1 bugs
A random reboot here and there
REPORTING BUGS
Source: JellyTime
Code:
How To File a Bug Report with Logcat:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb logcat' without the quotes
[*] Start the app that causes the issues
[*] Wait for the app to close or get to the error
[*] Copy logcat contents and put in pastebin
[*] Copy pastebin links here
[/LIST]
How To Find Wakelocks:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb shell cat /proc/wakelocks > wakelocks.txt' without the quotes
[*] Copy contents and put in pastebin
[*] Copy pastebin links on your post
[/LIST]
How To Get dmesg logs:
[LIST]
[*] Install android sdk
[*] Install drivers for adb on PC
[*] Connect phone to PC
[*] Open cmd.exe or terminal
[*] Type 'adb shell dmesg > dmesg.txt' without the quotes
[*] Copy contents and put in pastebin
[*] Copy pastebin links on your post
[/LIST]
Before filing a bug report, please consider the answer to these:
[LIST]
[*] Is the bug reproducible?
[*] How do you reproduce it?
[*] What is the expected behavior?
[*] What actually happens?
[*] Are you on the default Kernel?
[*] Did you restore data of System Apps using Titanium Backup?
[/LIST]
CHANGELOG
Go and check out PAC's github -> vendor_pac
INSTALLATION / NOOB GUIDE
Unlock your bootloader, if you haven't done so.
Download this the latest version of this badboy!
Grab a copy of the latest GAPPS package
If you come from a stock rom, reboot to bootloader, flash the boot.img from the ROM zip.
Reboot to recovery
Do a "Factory Reset" if coming from any other ROM than the semi-latest version of PAC
Flash the ROM! /system will be automatically wiped during install, as in all good ROMs.
Flash GAPPS
Reboot
Enjoy!
DOWNLOADS
Grab the latest PAC-man HERE or HERE
Normal GAPPS
Inverted GAPPS
DAILIES
Since shortly, mint builds are also available on PAC's basketbuild, check it out here:
http://pacman.basketbuild.com/index.php?dir=main/mint/nightly/
FAQ
Q: My sound is way too low!
A: Find Pimp My Rom in the Play Store, and install xLoud with it. This can also bring back BE with unlocked bootloaders!
Q: Paranoid Android preferences do not work!
A: https://github.com/ParanoidAndroid/android_vendor_pa/commit/e99a9b192386ca186dfe5a52126ce6fbe7da79a5 - or grab one of the latest ParanoidAndroid ROMs and sideload /system/app/paranoidpreferences.apk
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
a BIG shoutout to these people:
szl.kiev and PACman Team
CM team
ParanoidAndroid team
AOKP Team
XDA for just about everything else
[vertigo] - for letting me carry on with the ROM, and his initial work on PAC for XT.
If you think you need to be thanked, just let me know
Have you got your hands on another xperia T yet?
This looks good though, nice work
Not got another one yet, but I have had this tester running it over last couple of days, so I know it works He's also got Paranoid Android 2.55 to test so once I know that's ok I will update other thread too
You should get your hands on an TX, and make roms for those!
Sending from pacman ROM.
I have been testing pacman and have only had one issue as mentioned in OP, WiFi hotspot won't connect to my tablet..
This ROM is fast stable and very user friendly, really is best of all breeds.
Wifi is seamless, no having to reboot WiFi for first connection
If anyone has any functionality questions they want to know before installing please ask
Edit. I have been using original gapps not the 4.2 so can't verify that yet..
2nd edit. Had no issue with SD permissions either, no having to wipe internal SD which is a massive plus
Sent from my Xperia T using XDA Premium HD app
Is there a way to incorporate the Sony launchee, facebook intergration and Timescape?
Realy love cm aokp and pa, still don't want to lose some stock Sony stuff.
Can you please try? Or tell me (a noob dummy) how I can achieve this.
It was a probleme on my x10, x arcs, xs hope it will be history with the xt.....
Sent from my LT30p using xda premium
Its an ongoing problem that can't be solved in the long run. You can still tin time scape, but no widgets
Sent from the future on my Star Trek communicator.
Sent from my LT30p using XDA premium.
gregbradley said:
Its an ongoing problem that can't be solved in the long run. You can still tin time scape, but no widgets
Sent from the future on my Star Trek communicator.
Sent from my LT30p using XDA premium.
Click to expand...
Click to collapse
That's why I thought maybe it is possible to use xperia home as launcher.
ok, if that wass posseble the would do it...
thanks!!
I keep getting the recurring problem of not being able to connect to WiFi. It only happens on custom ROMs and I'm not sure what I can do about it. Anyone got any ideas?
xL3thalTuRdZz said:
I keep getting the recurring problem of not being able to connect to WiFi. It only happens on custom ROMs and I'm not sure what I can do about it. Anyone got any ideas?
Click to expand...
Click to collapse
keep rebooting each time it fails. It takes me 3 reboots to get it done. Once its connected the first time you dont get the problem again.
All this time I've been switching from great ROMs when the problem was easy to fix all along?
It's amazing how 'turning it off and on' can fix so many issues!
EDIT: Oops! Forgot to thank.
Sent from my Xperia T using xda app-developers app
Xperia TX port on this? I'd love to test it out.
i only have xperia TX, can you remove it for us? thx
The Rom have in the screenlocker settings a bug.you press the first button oft three and he close ever then the Menü.
Sent from my Xperia T using xda premium
I've been testing this Rom for a while and decided to use it as my daily Rom. Beautiful, quite stable, and fast. I have some bugs with audio. I think there is only one channel (some sounds are missing) on phone speaker. But I can live with it 'cos everything is fine when I use headsets. Almost everything is fine...
This is my biggest problem with this rom. I cannot answer the calls with the headset button. I' ve tried many different headsets and always the same problem. It is happening on all PA roms and CM rom. Can anyone help me to solve this problem?
Sent from my Nexus 7 using xda app-developers app
cube76 said:
I've been testing this Rom for a while and decided to use it as my daily Rom. Beautiful, quite stable, and fast. I have some bugs with audio. I think there is only one channel (some sounds are missing) on phone speaker. But I can live with it 'cos everything is fine when I use headsets. Almost everything is fine...
This is my biggest problem with this rom. I cannot answer the calls with the headset button. I' ve tried many different headsets and always the same problem. It is happening on all PA roms and CM rom. Can anyone help me to solve this problem?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well as this is based on CM and so is PA, its not going to be fixed in this until it is fixed in CM
Would like to wish all you guys a very Merry Christmas.... from all at the 3 Musketeers
right currently using v19.3 of PAC rom and my i be the first to say its the fastest PAC rom to date possibly the fastest 4.1.2 cm10 based rom on XT. it is that quick.................no lags even i market and thats saying something guys. this will be updated today to keep things alive in here. and before you ask i have tried them all and this is faster .............. trust me! no wifi connection issues at all now as connected first time and everytime
- when i got my XT i unlocked bootloader and flash cwm recovery not one from custom stock kernel but standalone version. i then installed siyah kernel and flashed curiosity stock rom. then after few days i flashed boot.img from PAC via fastbbot then reboot to recovery and flashed new PAC.
VERY FAST ROM and i am not joking!
Right guys I know there has been a delay but... here it is the new version
PACman v19.3.0
Now Enjoy
O
{
"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"
}
If you'd like to use this ROM as a base for a new ROM, please ask me first. Chances are very good I won't care.
ParanoidAndroid!
AOKP!
CyanogenMod!
GO PAC!
With your powers combined, this is PACman!
Disclaimer: I do not claim to be a developer... However, by READING, SEARCHING, and TRYING, I've learned some tricks of the trade. One of them has been building from source. All I am doing is putting a few pieces together to make it compile, all the hard work has been done by h8rift and mg2195. Their repos, hard work, and dedication build this ROM - all thanks/credit goes to them as well as the PACman, CM, AOKP, and the PA teams. Being that this is built off of h8/mg's trees, any bugs present in the CM10 ROM will be present in this ROM. The box that I compile on is by no means speedy, so updates will come when there are major breakthroughs, as soon as I can get them built. Feel free to post bugs, but please don't expect them to be addressed quickly, especially if it's not on h8's or mg's to-do list - like I said, I'm not a developer, but I will be tinkering – but with 4 kids, a full time job, a house to manage, and a build PC that’s years behind the game, play time comes sparingly. I test these builds on my own device before any release, but I do not claim it will work for everyone. ALWAYS have a nandroid in case of emergencies. I am NOT responsible for bricked devices or catastrophic failure
SCREENSHOTS
INSTRUCTIONS
Code:
[LIST]
[*] You must have your bootloader unlocked with a custom recovery (WCX Recovery tested, approved, and recommended)
[*] Download the ROM .zip and gapps .zip from the Downloads section, to either your Internal or SD memory
[*] Boot to recovery and wipe Data, Cache, Dalvik Cache, and System
[*] Flash ROM .zip
[*] Flash gapps .zip
[*] Reboot
[*] IF YOU ARE S-ON, you need to manually flash boot.img from Fastboot so -
[LIST]
[*] Extract boot.img from ROM .zip to the directory on your computer where fastboot is
[*] Boot to bootloader (PWR and Vol- from off state)
[*] Select Fastboot
[*] Plug your USB cable in and open a command prompt in the same directory you have fastboot
[*] Fastboot flash the boot.img (I like to flash it twice, just to be sure)
[CODE]
fastboot flash boot boot.img
[*] Reboot
[/LIST]
[/LIST]
[/CODE]
DOWNLOADS
Code:
[URL=http://www.mediafire.com/?6hka1s4vg5l4xq9]holiday_PAC_0210_unofficial-v19.3.0.zip[/URL]
[URL=http://www.goo.im/gapps]gapps[/URL] (you want jb-20121011)
RECOMMENDATIONS/MY PREFERENCES/TIPS
I've chosen not to incorporate these things into the builds, as they are easy enough to do on your own, and I didn't want to shove my preferences down others throats. Feel free to ignore any and/or all of these.
Code:
- Use a different launcher. I like Holo Launcher, I'm sure others work as well - but Trebuchet/Launcher2 seems
kinda choppy compared to alternate launchers.
- Use a different file browser. I use JRummy's Root Browser, find his thread on XDA for getting
rid of the ads. Again, I'm sure others work as well. CM's file manager is included - if you choose
to use it, make sure you enable Root Access in settings. I feel like other browsers are
currently superior to CM's, but YMMV
- Find a flashplayer 11 apk (available all over the web) and install it.
- Turn off keyboard vibrations (language and input in settings). Typing seems way more smooth (as it
always does on every device I've ever used)
- Turn on Developer Options in settings, and turn on Android debugging. Also in Developer Options,
choose Root access, and set it to Apps and ADB
- Allow installation of apps from Unknown Sources in Settings > Security
- You can find a quick guide for using Paranoid Settings here ([url]http://forum.xda-developers.com/showpost.php?p=35018434&postcount=2[/url])
NOT WORKING
Code:
- 720/1080p playback hiccups sometimes and tells you it can't play the video. Just restart it.
Also, fast forwarding 720/1080 isn't working great either.
- Can't adjust in call volume. The slider moves, but volume level stays the same.
- Currently some users have reported that the remote party hears themselves echo in a
call
- You tell me
CHANGELOG
Code:
02.10.13
- OC to 1.72
- h8rift's bluetooth fix (tethering, A2DP, calls, battery)
02.05.13
- Sources updated
- Added 4.2 Camera/Gallery
- Full Screen Viewfinder
- Working Panorama/Photosphere/Edit
- Working Picasa Web Album Sync
- Hopefully enabled stereo recording in 720/1080p video
- Fixed 1080p timelapse recording (if anyone uses it)
- Updated Kernel
- UV to 750000
- badass, smartassv2, and lag free governors
- V(R) and BFQ I/O Schedulers
- Imported qdsp6v3 (Rezound) audio drivers
01.28.13
- CPU properly clocked to 1.5 for everyone
- User Controlled Voltage (max 1350mV, min 812.5mV)
- CPU States File enabled,
- Default gov changed to interactive, set to Max 1.536 Min 192
- The flashable boot.img/modules is in the Downloads Section. If you're S-On, you need
to flash the .zip, as well as fastboot flash the boot.img. Use CPU Spy to view CPU States,
and System Tuner for Voltage Control. Definitely wipe Dalvik, and a wipe of cache isn't a
bad idea.
01.22.13
- PAC v19.0.0 - v19.3.0 (I'll try and find some more information about actual differences :))
- Includes boot.img with OC and external storage USB fix
01.15.13
- New boot.img only. This fixes the problem where external USB storage wouldn't mount
to your computer. The download is in the downloads section.
01.08.13
- Fixed issue where ATT in call mic didn't always initialize first call after flash or reboot
- Default APN for ATT users will now be PTA (LTE)
- Kernel now has CPU clock speeds available up to 1.512, where it should be
01.03.13
- Enabled 1080p recording/playback. This does not make the camera perfect.
There are still some problems with 720/1080 recording (the occasional
tearing/glitchiness we've always had), but a step in the right direction.
12.28.12
- Official PACman is no longer in Alpha, and has updated from v18.0.0 to v19.0.0
12.26.12
- h8rift found a temporary fix for the bluetooth battery drain. It will still drain when
Bluetooth is on, but will no longer drain as long as bluetooth is off
12.20.12
- Thanks to h8rift, we now have bluetooth (connects and pairs, but no a2dp yet), crt off animation, battery stats are
available, and USB transfer speeds have been increased.
- Updated PAC and device source
REPORTING BUGS
Code:
[LIST]
[*]Search to make sure it hasn't been addressed
[*]Don't sound like my whiny 5 year old
[*]Perform a full wipe (data, system, cache, and dalvik) and reflash the ROM. Verify the issue persists before installing any apps or backups
[*]Take this work for what it is - and follow h8 and mg's work in the CM thread for progress updates, and give them many praises and thank yous.
[/LIST]
CREDITS
Code:
[LIST]
[*]The Three Musketeers who created this beauty
[LIST]
[*][URL=http://forum.xda-developers.com/member.php?u=1862333]vertigo[/URL]
[*][URL=http://forum.xda-developers.com/member.php?u=4236487]Benjamin.j.Goodwin[/URL]
[*][URL=http://forum.xda-developers.com/member.php?u=1192722]Shingers5[/URL]
[/LIST]
[*][URL=http://www.aokp.co/]AOKP Team[/URL]
[*][URL=http://www.paranoid-rom.com/]Paranoid Android Team[/URL]
[*][URL=http://www.cyanogenmod.org/]Cyanogenmod Team[/URL]
[*][URL=http://forum.xda-developers.com/member.php?u=2703964]h8rift[/URL] for saving the day, and providing his sources
[*][URL=http://forum.xda-developers.com/member.php?u=4370145]mg2195[/URL] for keeping the project alive, and providing an excellent tutorial for compiling/building
[/LIST]
htc-msm8660 git
PAC-man git
ParanoidAndroid Merged Commits
AOKP Merged Commits
CM10 Merged Commits
My git so you can follow along at home with my amateur moves, however if the changes are proper and I feel worthy, I will ask h8rift if they should be merged. That is up to h8rift and intervigil. In the meantime my git is experimental (and only tracking kernel changes)
A very SPECIAL thanks to:
jtsurfs
davebegue (x3)
lucasryan
garrykd
Now all I need is at&t in call mic
Sent from my HTC Holiday using Tapatalk 2
Homeslice your the man for making these roms
sent from my HTC Vivid
H8rift and mg2195 are to thank. Can't stress that enough. Without them you can forget about these ones.
So many ROMS XD. Kudos to the devs for not giving up on the vivid
Well, now that I see what PAC man is, I'm interested in trying this too! (when time allows)
I just loaded this rom on my Inspire when my Vivid bricked. I loved this ROM for the day and half I rolled it. Eagerly awaiting some of the bugs to be ironed out to make this my daily driver.
Fix for camera. Flashable in recovery.
http://www.mediafire.com/?8xj4vbro7271xkb
homeslice976 said:
Fix for camera. Flashable in recovery.
http://www.mediafire.com/?8xj4vbro7271xkb
Click to expand...
Click to collapse
nice
New version with fixed wifi and camera fix included will be uploading soon
Edit: Uploaded. OP updated. Full wipe recommended
so its like cm10+aokp+PA in one rom? if so, niceeeeeeeeeeeeeeeeeee
i have problem with wifi yet
i have this problem with ics custom roms
in ics when i install a new custom rom, i must install 'wifix manager' to fix wifi
in jelly bean wifix manager doesn't work for me because can't install it's driver
if you guys don't have problem with wifi, i think i have old problem (need wifix manager)
edit: i think this app change my wifi region code
my problem solved. in wifi advance menu, you can change wifi region code. i set it to china
I get horrible batt. Life even when wiping everything especially when screen is on but not doing anythig processor intensive
Sent from my Holiday using xda app-developers app
I noticed since last update battery life has detereated a bit, but still as good if not better than Pegasus ICS rom
sent from my rooted, S-Off HTC Vivid 4G \o/
running CyanogenMod 10 JellyBean 4.1.2
Has to be placebo or a bad flash cause nothing changed that would affect battery good or bad...unless you're using the camera a bunch
ATT in call mic fix..
It seems it doesn't initialize with the first call, but each call after that I've tried I've been audible
http://www.mediafire.com/?ko0r125knhppo91
Flashable in recovery for S-Off users, S-On users will need to fastboot flash boot.img that's included after flashing this in recovery.
i know it's not 100%, but closer i guess
I'll have full builds up later today
homeslice976 said:
ATT in call mic fix..
It seems it doesn't initialize with the first call, but each call after that I've tried I've been audible
http://www.mediafire.com/?ko0r125knhppo91
Flashable in recovery for S-Off users, S-On users will need to fastboot flash boot.img that's included after flashing this in recovery.
i know it's not 100%, but closer i guess
I'll have full builds up later today
Click to expand...
Click to collapse
I was reading your post in CM, does this fix break wifi?
Nope
Sent from my Holiday using Tapatalk 2
Just flashed the new kernel and this ROM. Everything is working perfectly. Camera WiFi and att in call mic worked great in the first call I made.
Thank you and all the devs for all your hard work.
Sent from my Holiday using Tapatalk 2
SWEET....Early christmas for jason!! Your the man Homslice...thank you for your hard work, and also want to thank Mg and H8!!
DISCLAIMER
You need to have an unlocked bootloader to use this ROM & kernel. Also I or any contributor in the software DOES NOT take responsibility of damages caused to your phone due to this ROM.
{
"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"
}
1. Copy ROM zip and gapps zip to sdcard
2. *if your kernel has no recovery* extract boot.img from ROM zip and flash to device using command
Code:
fastboot flash boot boot.img
3. Reboot device and go to recovery by pressing Vol-UP when LED is pink
4. If coming from 4.1 or 4.0 ROM wipedata/factory reset your phone
5. Flash ROM zip
6. Flash Gapps zip
7. Reboot and enjoy.
Official Nightlies (automatically built every 4 days on AOKP buildbox) :
http://goo.im/devs/aokp/hayabusa/nightly
http://androtransfer.com/?developer=AOKP&folder=hayabusa/nightly
Unofficial Test Builds (will contain experimental changes for testing) :
http://goo.im/devs/kxp/hayabusa
http://uploaded.net/folder/5c8p9i
Gapps :
http://goo.im/gapps/gapps-jb-20130301-signed.zip
We spend countless of hours doing this for next to nothing. Posts, views, and donations encourage me, and everyone else who helps out.
Donate to AOKP
Donate to CyanogenMod
Every donation is cherished and loved.
If you'd like to help contribute by writing code, feel free to stop by IRC and talk to us!
http://kxp.championswimmer.tk/updates/changelog/
Check out the ROM source on github. Open source, in the spirit of community kangage.
CREDITS
I cannot thank more for the hard work of FreeXperia Team (@Jerpelea, @Bin4ry, @Kali-, @Entropy512, @codeworkx and others) for working on Xperia devices.
Also huge thanks to Sony Mobile AB for having been very developer-friendly and helping us in all sorts of ways.
nor I nor anyone involved in FXP owns a TX yet. So releases are blind and untested in nature.
just when I re-locked my phone and this comes out LoL
will give this a go when i get bored with stock again
And btw, how I wish Sony at least gives FXP team one piece of every phone models they have.
FXP has been very loyal to them, and considering the fact that Sony is very dev-friendly and always helps on drivers and everything.
Rycon33 said:
just when I re-locked my phone and this comes out LoL
will give this a go when i get bored with stock again
And btw, how I wish Sony at least gives FXP team one piece of every phone models they have.
FXP has been very loyal to them, and considering the fact that Sony is very dev-friendly and always helps on drivers and everything.
Click to expand...
Click to collapse
why did you relock ?
i flash stock on my V when I need to take pictures, but I never relock it
btw I would be very thankful if someone could test this one. especially if the touchscreen and vibrators are working or not.
i updated the kernel somewhat blindly based on the T and it's differences with TX
Re: [AOKP][JB4.2] {TX} KangXperiaProject
championswimmer said:
why did you relock ?
i flash stock on my V when I need to take pictures, but I never relock it
btw I would be very thankful if someone could test this one. especially if the touchscreen and vibrators are working or not.
i updated the kernel somewhat blindly based on the T and it's differences with TX
Click to expand...
Click to collapse
I am actually just readying my phone for an official JB update. Though I know ftf file will be available here very fast once JB comes. Anyways, it's easy to unlock again also.
Just a quick question, is the auto-brightness working? Or does it work on your V or T running aokp?
I'll probably flash this on the weekend and try.
Edit: I changed my mind, I'm currently enjoying the long-awaited official JB update(finally) and maybe I won't try this Rom for the mean time.
Tapatalked from my TX
Rycon33 said:
I am actually just readying my phone for an official JB update. Though I know ftf file will be available here very fast once JB comes. Anyways, it's easy to unlock again also.
Just a quick question, is the auto-brightness working? Or does it work on your V or T running aokp?
I'll probably flash this on the weekend and try.
Tapatalked from my TX
Click to expand...
Click to collapse
auto brightness works on T and V
Camera does not work. When you call the camera, an error that the application is stopped.
Flash in general is very slow.
The sound volume can not be adjusted, when the music player - a smartphone restarts
There is no file manager.
The mobile network is not available at all.
Brightness does not work.
The inscription "XPERIA" is off.
Initially, the screen was upside down and did not work touch.
After editing build.prop it worked.
nnmka said:
Camera does not work. When you call the camera, an error that the application is stopped.
Flash in general is very slow.
The sound volume can not be adjusted, when the music player - a smartphone restarts
There is no file manager.
The mobile network is not available at all.
Brightness does not work.
The inscription "XPERIA" is off.
Initially, the screen was upside down and did not work touch.
After editing build.prop it worked.
Click to expand...
Click to collapse
thanks for reporting
leds, backlight, touch shall be fixed
http://review.cyanogenmod.org/#/c/34496/
change has been merged ^^
also GSM shall work in next build (i forgot to merge entropy512's patch in time )
uploaded another build right now
please retest and report back
EDIT: the 26mar2012 build i mean
championswimmer said:
uploaded another build right now
please retest and report back
EDIT: the 26mar2012 build i mean
Click to expand...
Click to collapse
A very long time to boot, startup screen upside down, and sensor buttons do not work. Screen backlight blinking.
After editing the build.prop and delete rows svrotate, flash does not boot at all.
nnmka said:
A very long time to boot, startup screen upside down, and sensor buttons do not work. Screen backlight blinking.
After editing the build.prop and delete rows svrotate, flash does not boot at all.
Click to expand...
Click to collapse
could you provide a kmsg/dmesg and a logcat ??
championswimmer said:
could you provide a kmsg/dmesg and a logcat ??
Click to expand...
Click to collapse
How to do it? In the evening do.
Code:
adb logcat -d > log.txt
and for kmsg
Code:
adb pull /proc/kmsg
now send me log.txt and kmsg files
championswimmer said:
Code:
adb logcat -d > log.txt
and for kmsg
Code:
adb pull /proc/kmsg
now send me log.txt and kmsg files
Click to expand...
Click to collapse
To do this you need to connect your phone to your computer and then register through the console commands?
nnmka said:
To do this you need to connect your phone to your computer and then register through the console commands?
Click to expand...
Click to collapse
yes
Now, after the firmware is loaded on boot logo and nothing happens, constantly blinking lights.
How much time should pass the command: adb pull / proc / kmsg?
I waited 15 minutes, but it was never completed.
Wipe done, format the internal memory too.
Logs
A friend is the same.
http://kxp.championswimmer.tk/2013/04/aokp-jb-mr1-milestone-1/
new milestone, and new webiste
enjoy
http://goo.im/devs/kxp/jb-mr1/hayabusa/aokp_hayabusa-ota-eng.kxp-jb-mr1-2013-04-19.zip
(please let me know what are bugs )
When you select a ring tone, the phone either restarts or hangs.
The camera shoots poorly, the entire image is floating.
Auto Brightness is not working.
off label XPERIA.
When working with the sound of the phone reboots or hangs.
When playing a video, the GUI Android write error and restart the UI.
http://forum.xda-developers.com/showthread.php?t=2182679
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), 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.
*/
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.
What are UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
Latest build:
http://www.mediafire.com/?mzjrx8sxmigzl
Google Apps:
PA Team: http://forum.xda-developers.com/showthread.php?t=2397942
CM Team: http://d-h.st/users/dhacker29?fld_id=27426
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/CM10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
Display issues in Browser & other embedded webviews (Google Chrome works fine)
No access to TV-Out menu
Layout issues in lockscreen
Can only mount 1 sdcard on PC
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Color calibration & vibration intensity does not get saved
Users of CM9/CM10/CM10.1 may have to upgrade to CM10.2 first if they face set_metadata_recursive error during install
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Changelog
20131116
Initial release
Credits:
Nelson - Team Passion - Join Us on FB for Android related and friendly discussions!
FaultException, Pawitp and CyanogenMod Team
All users and developers contributing to development
Enjoy!
-- Reserved --
-- * Reserved *--
Good Job.
excelent...
Downloading, will post about ROM features later.
Now, i can menage to port ROM's with more features, because of you.
You are best
Nice thanks 4 this.. will try asap.
Sent from my SAMSUNG-SGH-T959 using xda app-developers app
after some using of ROM
ROM is totaly OK.
I know it was hard work, and thank you.
BAD THINGS:
1. Its little buggy, slow, with some '' better '' kernel, it should fly.
2. Hmm, icons, are stocks like in 4.3.1 Android, except camera, settings and and voice search.
3. Menu icons, are in 6x4, it look very ugly for me.
4. Camera is buggy. - NO 720p record -
5. Status bar pulling down is buggy to.
GOOD THINGs:
1. New dialer, very good.
2. After log into play store, you got new Gallery from Google, editing pictures very exposed and good.
3. New keyboard +
4. Other 4.4 goodies.
SCREENSHOOT:
{
"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"
}
Galaxy3HELL said:
ROM is totaly OK.
I know it was hard work, and thank you.
BAD THINGS:
1. Its little buggy, slow, with some '' better '' kernel, it should fly.
2. Hmm, icons, are stocks like in 4.3.1 Android, except camera, settings and and voice search.
3. Menu icons, are in 6x4, it look very ugly for me.
4. Camera is buggy. - NO 720p record -
5. Status bar pulling down is buggy to.
GOOD THINGs:
1. New dialer, very good.
2. After log into play store, you got new Gallery from Google, editing pictures very exposed and good.
3. New keyboard +
4. Other 4.4 goodies.
Click to expand...
Click to collapse
Thanks for the review.
I can look into fresh start of kernel later on.
Remember, CM has just started work over KK sources... merging of features is still in progress and this may take some time.
According to me, it is more fluid than JB which will let me keep this as daily driver.
neobuddy89 said:
Thanks for the review.
I can look into fresh start of kernel later on.
Remember, CM has just started work over KK sources... merging of features is still in progress and this may take some time.
According to me, it is more fluid than JB which will let me keep this as daily driver.
Click to expand...
Click to collapse
yeah, you are probably wright.
I,m sure that kernel will solve lots of problem.
Take look at mackay kernel on i9000 forum, he also have 4.4 KitKat ROM.
Fluid, it is, but Vanir 4.3.1 is at the moment most fluid rom on this forum.
Don't get me wrong, great ROM, love you.
Bye!
Galaxy3HELL said:
yeah, you are probably wright.
I,m sure that kernel will solve lots of problem.
Take look at mackay kernel on i9000 forum, he also have 4.4 KitKat ROM.
Fluid, it is, but Vanir 4.3.1 is at the moment most fluid rom on this forum.
Don't get me wrong, great ROM, love you.
Bye!
Click to expand...
Click to collapse
I can compile Mackay, if required.
neobuddy89 said:
I can compile Mackay, if required.
Click to expand...
Click to collapse
That would be great
Can you do that?
Awesome ROM Neo! I'm trying it right now and its really AWESOME! Enabled ART asap; apps open quick and are generally fluid. (Hangouts stutters when scrolling though) Scrolling over to Google Now stutters slightly, but thats to be expected with the first release. This is really good! Stable enough to be daily driver for me :good:
mackay has to be compiled from inside rom source.
cannondaleV2000 said:
mackay has to be compiled from inside rom source.
Click to expand...
Click to collapse
I can change that.
Downloading mackay kernel as zip file since I can't fork it as I already have forked one from CM.
I forgot to add FaultException to Credit list... adding..
neobuddy89 said:
I can change that.
Downloading mackay kernel as zip file since I can't fork it as I already have forked one from CM.
Click to expand...
Click to collapse
cool i thought about doing that but never had time to really look at it. would you mind sharing the parts needed for standalone build after you get it working? i want to build the kernel for my cappy.(hardbricked my vibrant) but i dont want to sync all the source since i dont maintane roms
cannondaleV2000 said:
cool i thought about doing that but never had time to really look at it. would you mind sharing the parts needed for standalone build after you get it working? i want to build the kernel for my cappy.(hardbricked my vibrant) but i dont want to sync all the source since i dont maintane roms
Click to expand...
Click to collapse
I will share on github if ready.
However, you may need to take care of its ramdisk which I believe should be same.....
Great start, appreciate your work.
got error status 7 coming from vanir. even tried flashing right after but still failed. tried rebooting recovery while while still in same session then was greeted by a message saying i lost root and gave me an option to flash su so i did, after doing so my phone rebooted on its own then finally some progress as i seen the cm splash screen then went into recovery which happen to be a new one. proceeded to flash tom again wiping everything minus sd flashed rom, install finally went through.
this is just about the fastest this phone has been since cm7, really...
stock cam fcs, at least with PA gapps
and for some reason, I cant get the ok google to work with this phone..tried updating search and everything
daily driver worthy, however
laylovj said:
this is just about the fastest this phone has been since cm7, really...
stock cam fcs, at least with PA gapps
and for some reason, I cant get the ok google to work with this phone..tried updating search and everything
daily driver worthy, however
Click to expand...
Click to collapse
Stock Cam working fine here with CM gapps. 720p definitely working.
To enable ok google, lockscreen widgets, and transparency in the status bar, you have to delete ro.config.low_ram=true from the build.prop. Neo mentioned this in the OP under FAQ. OK Google and the rest work perfectly fine after deleting it. :good:
Hobbesfed said:
Stock Cam working fine here with CM gapps. 720p definitely working.
To enable ok google, lockscreen widgets, and transparency in the status bar, you have to delete ro.config.low_ram=true from the build.prop. Neo mentioned this in the OP under FAQ. OK Google and the rest work perfectly fine after deleting it. :good:
Click to expand...
Click to collapse
never was a reader..still am not
anyway, reflashed again and PA gapps stock cam seems to work now..weird.
Hey there! I'm just a builder who want to share with all of you the compiled sources of Paranoid (Credits to the team for all the work and gerrit patches I've used).
It's an alpha, so it doesn't have many features:
- It has an advanced power menu with options to reboot (recovery, bootloader, reboot), screenshots, etc.
- Head-up notifications have been improve (using Hover sources I guess)
- Ambient Display has been added for our device too (replacing peek at this moment)
- Quick unlock is enabled.
- Quicksettings' tiles reorder
- Inmersion mode with tile support
- OnTheSpot is now implemented, but there isn't any example of it.
- ParanoidOTA comes with the rom, but isn't functional right now.
- Another smalls changes and improvements.
- CM12 Theme Engine
- Linked volumes and expandable volume panel
- Added a standalone File Manager
If you want to check all the new stuff of every build please visit gerrit. It works fine with TWRP and also multirom.
All the builds like build 4 or newer, will be compile from sources, without adding any feature, so they will be clean builds. I will try to get new ones every month until the team release their own ones, so enjoy them, and if you like my work, click Thanks #StayParanoid
Links
ROM(build 5): https://goo.gl/AvVlwz
GERRIT(changelog): http://goo.gl/wZamJf
GAPPS: http://goo.gl/kNcpB7
ROOT:http://goo.gl/DUhWyI
Installation
- Download the rom, the gapps you prefer and the root zip.
- Do a factory wipe in recovery (if you are updating from a previus paranoid 5.1 build just wipe dalvik&cache).
- Flash the three zips in the same order as above.
- Reboot and enjoy the rom!
Old Builds
Build 1 (11/01): http://goo.gl/kRMTBV
Build 2 (18/01): http://goo.gl/Xd6XXS
Build 3 (1/02): http://goo.gl/kLx10r
Build 4 (26/05): https://goo.gl/eaZg0O
Screenshots
{
"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"
}
One of my favorite ROMs since I moved to Android! Flashing for sure later! Moving to this ASAP xD
Sent from my Nexus 4 using XDA Free mobile app
damn, wont flash with twrp 2.8.3.2 ....
DJ_Uro_UE said:
damn, wont flash with twrp 2.8.3.2 ....
Click to expand...
Click to collapse
What's the problem?
Thanks bud!
Wooohooooo!!! It's finally coming!! :cyclops: Thanks for the build
many many MANY bugs with this...rotation does not work...even messes with rotation apps. Reboot menu only has reboot...no recovery or bootloader option. LTE 100% does not work...switch it on and loose data altogether. Rom will not flash in TWRP 2840...something about symlinks.
That's all I found before I got fed up and restored my factory backup. Seriously, thank you for taking the time to build and share this...I'm appreciative of that, believe me. This is just as far from usable for a daily rom as I've seen in a long time is all.
hp420 said:
many many MANY bugs with this...rotation does not work...even messes with rotation apps. Reboot menu only has reboot...no recovery or bootloader option. LTE 100% does not work...switch it on and loose data altogether. Rom will not flash in TWRP 2840...something about symlinks.
That's all I found before I got fed up and restored my factory backup. Seriously, thank you for taking the time to build and share this...I'm appreciative of that, believe me. This is just as far from usable for a daily rom as I've seen in a long time is all.
Click to expand...
Click to collapse
It's a shame that it has all this problems, but you have to remind that this is an alpha version , and for example you can find in gerrit patches for LTE that are in state of review, so if you want I can cherrypick them in next build.
About the powermenu options, you have to enable developer-settings, and there you will find an option to enable advanced reboot menu.
Finally with the build I will compile this saturday I will see what de can do to avoid the errors with the recovery, and also I will check the rotation.
yaymalaga said:
It's a shame that it has all this problems, but you have to remind that this is an alpha version , and for example you can find in gerrit patches for LTE that are in state of review, so if you want I can cherrypick them in next build.
About the powermenu options, you have to enable developer-settings, and there you will find an option to enable advanced reboot menu.
Finally with the build I will compile this saturday I will see what de can do to avoid the errors with the recovery, and also I will check the rotation.
Click to expand...
Click to collapse
Thank you. I totally understand it's a first build in early stages. I wasn't trying to beat you up...the problems could be in the source. I just wanted to let everyone know this shouldn't be expected to be a daily just yet, so they don't go in with high hopes and have them killed when all these things start going wrong. There are some builds that are definitely suitable as daily drivers as first-draft alpha builds, so it wouldn't be that surprising to find this one to be one of them, but unfortunately it's just not.
hp420 said:
Thank you. I totally understand it's a first build in early stages. I wasn't trying to beat you up...the problems could be in the source. I just wanted to let everyone know this shouldn't be expected to be a daily just yet, so they don't go in with high hopes and have them killed when all these things start going wrong. There are some builds that are definitely suitable as daily drivers as first-draft alpha builds, so it wouldn't be that surprising to find this one to be one of them, but unfortunately it's just not.
Click to expand...
Click to collapse
I must say that i'm running it without any problems at all.
Flashed successfully using TWRP.
Rotation is working fine.
So I would say go go go to all hesitating to update....
Thulin said:
I must say that i'm running it without any problems at all.
Flashed successfully using TWRP.
Rotation is working fine.
So I would say go go go to all hesitating to update....
Click to expand...
Click to collapse
Can you give us some screenshots please
Thulin said:
I must say that i'm running it without any problems at all.
Flashed successfully using TWRP.
Rotation is working fine.
So I would say go go go to all hesitating to update....
Click to expand...
Click to collapse
That's good to hear...would you please tell us what version of twrp you used? I tried 2840 and got the symlink error. I reverted back to 2820 since that's the newest I had stored on my pc and it flashed.....but with all these bugs I listed. Maybe it's not flashing properly still???
I had native rotation on and it didn't wok, so I downloaded Ultimate Rotation Control ( https://play.google.com/store/apps/details?id=nl.fameit.rotate&hl=en ) which works fine for me on 5.0.1 factory image....it was missing several rotation options with this rom, and the only option that worked was manual, which consists of a notification widget and clicking the angle of rotation you want, in order to change it....and it locks to that position. Like I said, maybe it messed up flashing...it definitely had some real issues. I'll try again and report back
---------- Post added at 10:40 AM ---------- Previous post was at 10:34 AM ----------
SebiC98 said:
Can you give us some screenshots please
Click to expand...
Click to collapse
It's nearly 100% stock AOSP, from the looks of it. It doesn't have any options besides the reboot menu, that I know of.
SebiC98 said:
Can you give us some screenshots please
Click to expand...
Click to collapse
Sceenshots of what, it's pretty much just stock lollipop at the moment. Nothing to show off....
TWRP: 2.8.3.0 was used.....
any one try it in multirom??
is it work??
qzxi said:
any one try it in multirom??
is it work??
Click to expand...
Click to collapse
Yep, I use it to test the builds
Build 2 is up, see gerrit for changes!
yaymalaga said:
Build 2 is up, see gerrit for changes!
Click to expand...
Click to collapse
How's the performance of this? Does it still have the launcher redraws due to memory leak?
Cool, I'm still waiting for some new stuff from PA
Thanks mate That´s what i was waiting for
jer_ying_fd said:
How's the performance of this? Does it still have the launcher redraws due to memory leak?
Click to expand...
Click to collapse
It's almost the same as a clean aosp rom. They have fixed memory leaks, but I don't remeber anyone about the launcher.