Develop Bugs

[ROM][June 17TH,2012][CM 7.2][Strawmetal.CM][V6]

This is based on the latest stable release 7.2 from Cyanogen.
This is a personal build and is my first attempt at customising CM.
{
"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"
}
Apks removed:
ADWLauncher
Androidian
Browser
CMStats
CMUpdateNotify
CMWallpapers
Cyanbread
Development
FileExplorer
Gallery3D
Music
Pacman
ProTips
QuickSearchBox
Click to expand...
Click to collapse
Apps Added:
AdAway
AdobeFlashPlayer
AdobeReader
BoatBrowser
Facebook
FasterGPS
GestureSearch
Google+
GoogleMaps
LauncherPro
PlayMusic
Pocket
QuickPic
SMS Backup & Restore
SolidExplorer
Talk2
TitaniumBackup
Twitter
WhatsApp
XDA
YouTube
Click to expand...
Click to collapse
Other Changes:
Included Updated Gapps
Elite Kernel by nik3r
Virtuous OC Daemon by virtuous
Zipaligned
EXT4 optimisation
Wipe EFS on flashing
Radio libs for 04.19
V6Supercharger U9RC8.2 Script extracted to sdcard
Busybox 1.20
Build prop tweaks
Debugging notification disabled
Default theme changed
Ringtones,Notifications sounds from HTC and MIUI included.
Bootanimation changed
LauncherPro icons changed
Click to expand...
Click to collapse
Instructions:
Full Wipe necessary(Superwipe)
First boot after install will be very slow. After it boots wait for some time or force close launcher pro. Also you may have to force close launcherpro after every reboot. UI might be slow after that which can be fixed inside launcher pro advanced settings
Play Store(if not present) will show up after adding your Google account in the settings menu.
Click to expand...
Click to collapse
Downloads:
Strawmetal.CM.V6
Strawmetal.CM.V5, MD5 = 689cf8f5aca476dd766bdaed60e7f61c
Strawmetal.CM.V4, MD5 = acb53c252dd66ca91cb8cb992e50a6ad
Strawmetal.CM.V3
Strawmetal.CM.V2
Click to expand...
Click to collapse

Hmmm. ROM looks very interesting
Test Time.
Downloading.
THX

zibiss said:
Hmmm. ROM looks very interesting
Test Time.
Downloading.
THX
Click to expand...
Click to collapse
<3 Strawmetal sauce. Is this a Sony theme? I love it!
---------- Post added at 01:10 AM ---------- Previous post was at 12:35 AM ----------
Getting a frozen white HTC screen with this:
Code:
I/AudioHardwareMSM7X30( 1513): Setting in-call volume to 100 (available range is
0 to 100)
E/AudioHardwareMSM7X30( 1513): msm_set_voice_rx_vol(100) failed errno = 1

Looks very well! Indeed nicely themed! Gonna try it out when I have the time

Quote nice this rom. Unfortunately, the airbnb search function is causing a force close. Can anyone else confirm? Or know why?
Sent from my HTC Vision using XDA

Ok, so it looks like I will download this... again!
Edit: Now I get a bootloop.

Bootloops.
logcat says this:
Code:
E/HTC Acoustic( 1493): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 1493): failed to open A2051 CSV files /system/etc/TPA2051_CFG.csv.
E/AudioHardwareMSM7X30( 1493): msm_set_voice_rx_vol(100) failed errno = 1
E/AndroidRuntime( 1507): *** FATAL EXCEPTION IN SYSTEM PROCESS: android.server.ServerThread
E/AndroidRuntime( 1507): java.lang.ExceptionInInitializerError
E/AndroidRuntime( 1507): at com.android.server.ServerThread.run(SystemServer.java:170)
E/AndroidRuntime( 1507): Caused by: java.lang.NumberFormatException: unable to parse '' as integer
E/AndroidRuntime( 1507): at java.lang.Integer.parseInt(Integer.java:362)
E/AndroidRuntime( 1507): at java.lang.Integer.parseInt(Integer.java:332)
E/AndroidRuntime( 1507): at java.lang.Integer.valueOf(Integer.java:506)
E/AndroidRuntime( 1507): at com.android.server.am.ActivityManagerService.getIntProp(ActivityManagerService.java:356)
E/AndroidRuntime( 1507): at com.android.server.am.ActivityManagerService.
<clinit>(ActivityManagerService.java:365)
E/AndroidRuntime( 1507): ... 1 more
E/AndroidRuntime( 1507): Error reporting crash
E/AndroidRuntime( 1507): java.lang.NullPointerException
E/AndroidRuntime( 1507): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
E/AndroidRuntime( 1507): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:854)
E/AndroidRuntime( 1507): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:851)

See, I'm wondering if the people who got it to work just flashed V2 over V1? Anyone who got it to work without having V1 installed first?
Edit: 4th download, using Chrome, Orbit downloader, and IE8/9. No difference.

nickeedoo said:
See, I'm wondering if the people who got it to work just flashed V2 over V1? Anyone who got it to work without having V1 installed first?
Edit: 4th download, using Chrome, Orbit downloader, and IE8/9. No difference.
Click to expand...
Click to collapse
I flashed V2 after superwipe and no issues at all... but i'll verify it a few more times and report....
EDIT: I took the screenshots on V2...(so it didnt bootloop for me)
EDIT: Made a superwipe again and it boots again without issues...I'll reupload the rom again... please look for it tomorrow at the latest...md5 will be posted

Hmm... try reuploading? Or making an md5? I did that on all the files I downloaded and they're the same every time.

Am I the only one who had a successful install of this rom? I came from ILWT, flashed data / cache then did superwipe+ext4 then wipe dalvik. It actually booted quite fast, In under 20-30 seconds it seemed.
Upon boot, the rom ran very smooth and quick. My only complaint was airbnb wasn't working, which it was working on ILWT, so I had to go back to ILWT. Shame because I really like this rom. Aside from the theme which I got bored of quickly. Thanks for the upload!! Good work.
Sent from my HTC Vision using XDA

Apparently, you must use superwipe before installing this rom. Simply going to "format all (except SD)" doesn't seem to work. Thanks! I'll test this right away!
Edit:
.... RAGE MODE ACTIVATED!! Adb says the following services died:
sensorservice
entropy
power
media.audioflinger
media.player
media.camera
media.audio_policy.
I see this line:
"Failed to open A2051 CSV files /system/etc/TPA2051_CFG.v"
Edit2: It works!

V3 Testing
V3 out for testing.
Changelog:
Included NeverGone\RU's earphone volume mod
Updated market apps
Bootanimation disabled for faster booting.
Instructions:
Wipe cache,dalvik if updating from V2
Full Superwipe necessary if flashing over any other rom...
REQUEST:
Please test if the volume mod is working and report any issues.
What is airbnb????
Will update this link into OP after you guys say its okay

strawmetal said:
V3 out for testing.
Changelog:
Included NeverGone\RU's earphone volume mod
Updated market apps
Bootanimation disabled for faster booting.
Instructions:
Wipe cache,dalvik if updating from V2
Full Superwipe necessary if flashing over any other rom...
REQUEST:
Please test if the volume mod is working and report any issues.
What is airbnb????
Will update this link into OP after you guys say its okay
Click to expand...
Click to collapse
Airbnb is just an app I use to search vacation properties when I go on vacation. But I use it often and it wasn't working. So I had to change roms. Not sure why it wasn't working. I'm back on ILWT and it's working fine again.
Sent from my HTC Vision using XDA

For some reason on minus its showing me that the file doesn't exit really want to try this out, I logged in and still no good. Hmm.
Sent from my HTC Vision using xda premium

mrbmg said:
For some reason on minus its showing me that the file doesn't exit really want to try this out, I logged in and still no good. Hmm.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
That's too bad, this rom is awesome! Minus worked for me using dolphin hd.
Sent from my HTC Vision using XDA

strawmetal said:
V3 out for testing.
...
Click to expand...
Click to collapse
Thanks! I couldn't get v2 to boot so will try this one tonight when I have some time to do so
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
Palingenesis said:
That's too bad, this rom is awesome! Minus worked for me using dolphin hd.
Sent from my HTC Vision using XDA
Click to expand...
Click to collapse
If you download with your phone sometimes it works to go to the normal page instead of mobile page.

Why is this downloading at 27 kb/s :| Lolololol

Again I cannot get it to boot, i have made a logcat, maybe this helps http://pastebin.com/5RYq648A I did a superwipe before installing.

Hagelslagje said:
Again I cannot get it to boot, i have made a logcat, maybe this helps http://pastebin.com/5RYq648A I did a superwipe before installing.
Click to expand...
Click to collapse
Sorry to hear that you guys aren't able to boot it .... Worked flawlessly for me V3 bootup was 14seconds on first flash... .... Anyways i'll build it from scratch again and see if that'll work for you.... Give me a day to do it because i just reverted to stock with no root(am making a sense version)...
Cheers...

[MODS/Q&A ] XenonHD ROM ALL DEVICES

{
"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 am going to fill this op with Questions and answers from all devices supported by Team Horizon. Please keep the respect and KEEP ALL NON DEVELOPMENT DISCUSSION HERE OR OUR
GOOGLE PLUS PAGE
Click to expand...
Click to collapse
.​
Click to expand...
Click to collapse
Q. I came from 4.1.2 and I flashed your 4.2.1 and I can't access my files now?
A. Well this is because after the 4.2.1 update Google implemented a feature with in its ROM to allow for the use to apply user specific accounts. I suggest reflashing a 4.1.2 ROM, Then mount the phone once booted, Take all of the information you choose to keep and place it on your desktop, Once complete then reboot the phone into recovery and wipe the rm and reflash 4.2.1 once you have flashed rom and gapps, Before you leave recovery wipe the sd card. Once phone reboots then simply replace the information you placed on your desktop to its corresponding folder.
Click to expand...
Click to collapse
Q. my wifi is always on when in standby?
A.Disable wifi optimization, And avoid poor connections in wifi advanced options.. If you have Franco kernel, wifi fast pm helps too
Click to expand...
Click to collapse
Q. HELP I don't have a rom on my SD card and I am stuck in a boot loop what do I do?
A. You need to make sure you have a working adb setup along with all proper fastboot and device drivers installed. Place the rom you wish to flash in the root of the adb folder.
Make sure phone is in recovery mode and that it is plugged into the computer.
Open a command prompt and cd to the directory of the adb folder. ( or simply hold the shift key and right click your adb folder and choose to open command windows here)
now type: adb push (rom.zip) /sdcard/ (replace the (rom.zip) with the entire name of the rom.zip.)
Click to expand...
Click to collapse
Q. How come fast charge is not working or its enabled but not working?
A. Answer is simple, The roms stock kernel doesn't allow for fast charge. you may simply flash Franco kernel and or any other 4.2.1 kernel that supports to to gain functionality.
Click to expand...
Click to collapse
Q. Can I dirty flash (flash ROM without wipe)?
A Yes you may flash the ROM without wiping. YOU WILL HAVE TO REFLASH GAPPS. We don't recommend doing this but if you are pressed for time or its just too difficult then have at it. We will not support complaints from those that choose to go this route.
Click to expand...
Click to collapse
Warez Removed
Q. I have downloaded the ROM but it wont boot?
A. Please make sure you are downloading the correct ROM and completely wiping before flashing!
Crespo- http://d-h.st/users/iceandfire/?fld_id=9532#files
Grouper- http://d-h.st/users/iceandfire/?fld_id=8701#files
Maguro- http://d-h.st/users/iceandfire/?fld_id=8699#files
Mako- http://d-h.st/users/iceandfire/?fld_id=9438#files
Toro- http://d-h.st/users/iceandfire/?fld_id=8700#files
Toro Plus- http://d-h.st/users/iceandfire/?fld_id=9002#files
Click to expand...
Click to collapse
Q. Somebody know, how to disable waking up phone by pressing volume button?I dont like this feature.
A. Menu>settings>display>enable then disable the volume key MOD
Click to expand...
Click to collapse
Q. Where are my Chrono settings for weather and clock?
A. Menu>System Settings>Display>Clock widget
Click to expand...
Click to collapse
Q. Are the round widgets shown in the OP contained in the ROM? If not, are they available anywhere? Also, I cannot for the life of me figure out how to put a lockscreen widget. When I go into the Chronus settings, there are settings for the clock, weather and calendar widgets, but I can only add the clock widget to my device.
A. OK the widget is not included but called one more clock widget. To apply the clock. Lock the screen then place your finger on the clock and slide down till you reach the lock icon or the white outline is the write screen amd let go. Then long press the clock ad delete it. Then click the add widget . After you enabled everything in display then go to chrono in the options onthe lockscreen (the + sign from earlier) and add it. To add muliple widgets then slide down on clock to fill screen then swipe left or right.
Click to expand...
Click to collapse
Q. What is fast charge? what does it do for me? How do I get it to work?
A.
Fast charge is a option baked into the kernel that doesn't allow the phone to be mounted to the pc.
Keeps computer from mounting your sd card everytime its plugged in.
You need to install a kernel that supports it. Stock XennonHD doesn't allow for this. I suggest using Franco Kernel. found here: http://forum.xda-developers.com/showthread.php?t=1367341
Click to expand...
Click to collapse
Q. What gapps do i install on this rom? I installed the gapps from ice not all my apps are there?
A.
Download these gapps: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Because all of the apps missing can be manually installed from the market. He did this to lighten the download.
Click to expand...
Click to collapse
Q. How to create a log cat
A. the code for logcat to output to a file is
adb logcat > name of problem.txt
you can also do
Click to expand...
Click to collapse
adb logcat -f name of problem.txt
how I prefer to do it is this way
Click to expand...
Click to collapse
:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
Click to expand...
Click to collapse
I then could do the following with logcat:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
Click to expand...
Click to collapse
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Click to expand...
Click to collapse
Q. I am in the download section but what rom is for my device?
A.
Crespo- nexus S
Grouper- Nexus 7
Maguro- gsm galaxy nexus t-mobile
Mako- galaxy nexus 4
Toro- Galaxy nexus Verizon Wireless
Toro Plus- sprint galaxy nexus
Click to expand...
Click to collapse
Click to expand...
Click to collapse
==================================================​
Important please read​
I. Appreciation
There are many ways to show your support to us. You can:
Press the "Thanks" button.
Hit the donation button and help support the team
Wear our specially prepared banner
Share your opinion about my work and write some feedback in our threads.
Advertise our work to your friends, family, anyone who owns this device.
Rate our threads with 5 stars.
We appreciate all the support you give us, but we don't expect anything
Click to expand...
Click to collapse
II. Sharing
XDA-Developers.com is all about sharing. If you would like to use any part of our work, please feel free to do so but remember to do the following beforehand:
Inform - Please send us a PM or email telling us
Permission - Please, if you do not have permission from us, don't use it. Most of the time, we will allow you to, but if you don't get our permission first, we will report.
Credits - No one wants their work stolen. Please remember to give proper credits when using our work.
Click to expand...
Click to collapse
:
III. Support
If you have any issues or questions, please feel free to post them in the our threads. However, because all of us have social lives outside of XDA, your questions may not always be answered right away. Members who are more experienced in our work, please help out the ones who don't.
If you want to get the fastest and the best answer - ask the question in our threads instead of PM'ing us. Chances are, other users will be able to help you when Team Members don't have the time to.
Click to expand...
Click to collapse
IV. Updates
We are a busy team! Every Team Member has lives outside of XDA. You cannot expect us to sit in front of the computer all day and develop Android. Please do not ask for ETA's. The update will come when we release it. Sometimes, there is a good reason for why we have not released an update in a while. Please be patient with us, we will do as we promise. Updates will come.
Click to expand...
Click to collapse
V. Responsibilities
We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.
Thanks for choosing Team Horizon, we hope you enjoy our works as much as we enjoy working with them.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

MOD Section
This is going to be a section where I post add ons for this ROM. Enjoy!
Click to expand...
Click to collapse
<---------http://dl.dropbox.com/u/44672998/supporter.png
My Dev-Host Account With All The Add On Downloads!
http://goo.gl/4rscI
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Invered Gapps! 4.2.1
CLICK ME
Click to expand...
Click to collapse
:highfive:

HELP!
Please Help Contribute To This Project. Either Post Question With Answer and I Will Add To OP or PM Me The Stoofz
:highfive:

Great idea Tory, You have been a real asset to the team, thanks for all you do.
Sent from my SCH-I535 using Tapatalk 2

I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2

crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am on latest franco and fixing to test wifi tether. hold (on gsm tho)

crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.

pr0xy mAn1Ac said:
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
Click to expand...
Click to collapse
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2

crispy1 said:
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please keep us posted on your progress. let me know if I can help.

Quick Unlock
Is quick unlock working? It has not worked for me for a while, but I saw one person say it works. I have done a full wipe with each version. Thanks!

pr0xy mAn1Ac said:
Please keep us posted on your progress. let me know if I can help.
Click to expand...
Click to collapse
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2

crispy1 said:
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD

crispy1 said:
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
edited
10char

Navigation bar opacity
I love the whole ROM, been using it for a while. I was very excited to see a translucent menu bar option in the 12/30/12 release. However im not sure of its functioning properly. On the home screen the nav bar is translucent however in any app its a solid black background again. When I zoom using accessibility feature (triple tap) the nave bar goes back to being all but invisible. Is this transparent effect only supposed to do what it does on my case? Thanks man, keep up the good work

Just a quick question pr0xy ... Do I have to wipe data in order to install inverted gapps or can i dirty flash over the 20121212 package? Thx in advance!

Just flash the gapps brother no wiping needed. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2

Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance

Doomhamma said:
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Click to expand...
Click to collapse
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2

pr0xy mAn1Ac said:
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
No it's not ... That's why I asked

*DUMB NEWBIE QUESTION*
how to flash this rom ?
just tried to flash the rom using TWRP, but it stucks at bootlogo.
now restored the rom and N4 is working normal.
any solution ?
thx in advance.

CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report

{
"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"
}
Opening this thread in order for the users to post their issues here instead of the development section or CM10 bug report thread.
This thread refers to discussions/bug reports for CM10.1 (Android 4.2.2) released by arco68 here.
As usual, it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.
On behalf of the SGW users, big thanks to arco68 and the CyanogenMod Team!
Great job, guys!
Note: bugs concerning custom kernels are to be reported into the corresponding threads! Please, don't post them here.
In order to avoid posting bugs that are not actually bugs, please, make sure you follow this little tutorial before upgrading/installing CM10.1:
For installation, first, make sure you got CM10.1 ROM and the correct Gapps on your External SD Card. Both can be found in the Mirrors section below.
After that, enter CWM and:
select "wipe data / factory reset"
go to "mounts & storage" and format /system. This is extremely important!
under the same menu, format /sdcard (be careful NOT to format /external_sd by mistake)*
install CM10.1 (from the external sd)
install Gapps for JB+ (from the external sd)
reboot your phone
* On newer CWM Recovery versions, you might find the internal memory mounted as /sdcard0 and the external one as /sdcard1. For this case, make sure you don't format /sdcard1 by mistake.
Please, note that every step of this tutorial is mandatory!
For apps backup & restore using Go Backup Pro, please, follow the tutorial below, step by step:
For Backup
1. Make sure you have an external SD card inserted
2. Download Go Backup Pro (of course)
3. Enter the app and go to Settings (from the 3 vertical dots on the right side of the screen)
4. Make sure that for the Backup Path, you have selected External storage (if I'm not mistaken, this is the default setting anyway, but it's good to confirm, just in case)
5. Go back and go to New/Restore Backup section
6. Click Batch Backup (bottom left of the screen)
7. Select what you want to backup*
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts.
8. Click Start Backup
9. Wait for it to finish and click Finish
For Restore
1. Assuming that by now you already have a backup to restore, go to New/Restore Backup section again
2. Click Batch Restore
3. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
4. Click on "APK + Data" from Restore Content and select "Restore app only". Now the Restore Content section will show only APK.
5. Uncheck the apps for which you need app data. Those apps won't be restored, for now. Please, go on with the tutorial.
5. Click Start Restore
6. Wait for it to finish and click Finish
7. Now that we chose what apps we want to be restored without app data, let's go back and enter New/Restore Backup section (yeah, again ).
8. Click Batch Restore
9. Uncheck everything*.
*Tip: to select/unselect all User Data, all System Settings etc, you have a checkbox on the same row with the actual User Data or System Settings texts
10. Now, pay attention to the User Applications section of that screen. Right underneath the User Application text, you have an option that says "Restore Content".
11. Click on "APK" from Restore Content and select "Restore app and data". Now the Restore Content section will show APK+ Data.
10. Check only the apps for which you DO need app data to be restored (the ones that were left unrestored from last time ).
11. Click Start Restore
12. Wait for it to finish and click Finish.
How to post a bug report:
Copy-paste the lines below in your post, filling up the required information:
HTML:
[B]Version:[/B] CM10.1 - Beta 4
[B]App/Game/Subject:[/B] WRITE HERE SUBJECT
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Probability of occurrence:[/B] WRITE HERE "LOW/MEDIUM/HIGH" (depending on how often the bug occurs)
[B]Description:[/B] WRITE HERE DESCRIPTION
Mirrors:
CM10.1 Beta 4 20140509 (MEGA): here
md5sum: c7e9114d760c0e924919b1be95425048
Gapps 20140507 JB+ (MEGA): here
md5sum: b0d6e6b62cb9149aea5de2531026f33a
Changelog Gapps:
Changelog Gapps 20140507:
* Google Search v3.4.16.1149292.arm
* Google Maps v8.0.0
* Hangouts v2.1.100(1151589-30)
* Google Play Services v4.3.25(1117461-034)
* Google Play Store v4.6.17
* Google Text-to-Speech Engine v3.0.11.1070024
Changelog Gapps 20140209:
* Google Maps v7.6.0
* Hangouts v2.0.303 (1004807-30)
* Google Play Services v4.1.32 (978161-34)
* Google Search v3.2.17.1009776.arm
Changelog Gapps 20131214:
* Google Maps v7.5.0
* Gmail v4.7.1 (946962)
* Google Play Services v4.0.34 (924341-34)
* Google Play Store v4.5.10
* Google Search v3.1.24.941712.arm
* Hangouts v2.0.217 (944332-30)
* Talkback Service v3.5.1
* Google Text-to-speech v2.4.3.864779
Changelog Gapps 20131001:
* Gmail v4.6 (836823)
* Google Search v2.8.8.849369.arm
* Google Hangouts v1.2.018 (849105-30)
Changelog Gapps 20130917:
* Google Maps v7.2.0
Changelog Gapps 20130825:
* Google Search v2.7.9.789824.arm
* Google Hangouts v1.1.2.778356
Changelog Gapps 20130817:
- Google+ (can be redownloaded from Google Play Store, if needed)
* Google Play Store v4.3.11
* Google Maps v7.1.0
Changelog Gapps 20130814:
+ Google Hangouts v1.1.1.753199**
+ Google Maps v7.0.2**
* Hangouts libs
* Google Play Services v3.2.25 (761454-34)
* Google Play Store v4.3.10
+ Google+ v4.0.2.48854689
**Re-added to the new base package from goo.im
Changelog Gapps 20130726:
* Google Hangouts v1.1.1.753199
Changelog Gapps 20130718:
* Google Play Services v3.1.59 (736673-34)
* Google Maps v7.0.2
Changelog Gapps 20130715:
* Google Talkback Service v3.4.0
Changelog Gapps 20130712:
* Google Maps v7.0.1
Changelog Gapps 20130630:
* fixed Hangouts video calling FC
Changelog Gapps 20130628:
* Google Search v2.6.7.721924.arm
* Gmail v4.5.2-714156
Changelog Gapps 20130624:
+ Google Street View (Google Maps addon) v1.8.1.2
+ minor changes
Changelog Gapps 20130612:
+ Gmail v4.5-694836 (the new, beautiful Gmail app)
+ Google Maps v6.14.4
* Google Play Services v3.1.36 (669520-34)
* Google Play Store v4.1.6 (the new Google Play Store)
* Google Search v2.5.8.675703 (the new Google Search with Google Now)
* Google Hangouts (ex Google Talk) v1.0.2.695251
* Google Talkback Service v3.3.2
+ means that the app was newly added
* means that the app was upgraded by replacing it with the newer version
- means that the app was removed
To enable Developer Options: go to Settings -> About Phone and tap the Build Number 7 times to enable Developer Options.
To enable Advanced Reboot options: go to Settings -> Developer Options and check the Advanced Reboot box.
Please, see the screens below for more information.
To swap memories (internal with external SD Cards) in Alpha 3 and above without modifying the vold.fstab file, go to /System/build.prop using any File Explorer with root privileges (recommended X-Plore) and change from 0 to 1 in the code below*:
Before
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Blue"]0[/COLOR]
After
Code:
# Change to 1 for swapping SD cards
persist.sys.vold.switchexternal=[COLOR="Red"]1[/COLOR]
*Thanks to Madridii for this.
Videos
Bugs reported/still occurring so far (Beta 3):
1. Camera/Gallery (To be confirmed in Beta 4)
Camera/Gallery app becomes unresponsive when locking&unlocking the screen multiple times (about 4 times in my tests). After that, if the user chooses to force close the Gallery app, when entering the Camera app again, he will be prompted with the following error message: "Can't connect to the camera".
Please, see the attached screenshot and the log below for more info.
Code:
[ 08-05 15:13:30.010 441: 456 W/ActivityManager ]
Activity idle timeout for ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}
[ 08-05 15:13:31.521 441: 503 I/InputDispatcher ]
Application is not responding: AppWindowToken{414fc260 token=Token{41691380 ActivityRecord{41225ca0 u0 com.android.gallery3d/com.android.camera.CameraLauncher}}} - Window{4122f110 u0 com.android.gallery3d/com.android.camera.CameraLauncher}. It has been 5003.1ms since event, 5001.2ms since wait started. Reason: Waiting because the focused window has not finished processing the input events that were previously delivered to it.
[ 08-05 15:13:31.531 441: 503 I/WindowManager ]
Input event dispatching timed out sending to com.android.gallery3d/com.android.camera.CameraLauncher
[ 08-05 15:13:31.621 441: 503 I/Process ]
Sending signal. PID: 5350 SIG: 3
[ 08-05 15:13:31.621 5350: 5355 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:31.701 5350: 5355 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:31.701 441: 503 I/Process ]
Sending signal. PID: 441 SIG: 3
[ 08-05 15:13:31.701 441: 444 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:31.882 143: 5647 E/CAM_FD ]
cam_conf: In config thread
[ 08-05 15:13:31.992 441: 503 I/Process ]
Sending signal. PID: 553 SIG: 3
[ 08-05 15:13:31.992 553: 560 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:32.002 441: 444 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.002 441: 503 I/Process ]
Sending signal. PID: 656 SIG: 3
[ 08-05 15:13:32.002 656: 670 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:32.042 553: 560 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.092 656: 670 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:32.212 441: 443 D/dalvikvm ]
GC_CONCURRENT freed 1916K, 21% free 10090K/12716K, paused 4ms+7ms, total 97ms
[ 08-05 15:13:32.212 441: 503 D/dalvikvm ]
WAIT_FOR_CONCURRENT_GC blocked 65ms
[ 08-05 15:13:32.422 441: 503 D/dalvikvm ]
GC_EXPLICIT freed 777K, 21% free 10132K/12716K, paused 4ms+5ms, total 91ms
[ 08-05 15:13:32.632 441: 1243 E/Sensors ]
type : 0, deley : 66667000
[ 08-05 15:13:32.632 441: 1242 E/Sensors ]
type : 0, deley : 20000000
[ 08-05 15:13:33.003 441: 503 I/Process ]
Sending signal. PID: 1051 SIG: 3
[ 08-05 15:13:33.003 1051: 1056 I/dalvikvm ]
threadid=3: reacting to signal 3
[ 08-05 15:13:33.103 1051: 1056 I/dalvikvm ]
Wrote stack traces to '/data/anr/traces.txt'
[ 08-05 15:13:33.113 441: 503 E/ActivityManager ]
ANR in com.android.gallery3d (com.android.gallery3d/com.android.camera.CameraLauncher)
Reason: keyDispatchingTimedOut
After rendering the Panorama shots, when the camera returns to the Panorama Mode for the user to take another panoramic shot, the camera preview is flickering. This happens only if the Auto-Rotate function is ON and the screen in Portrait mode. With the Auto-Rotate OFF, this bug does not occur.
Please, see the attached screenshot for, hopefully, more info on this.
Camera/Gallery app becomes unresponsive when taking a picture, sliding left to see the picture and tapping on it to see it in "full screen" then locking the screen for about 10 seconds. After that, if the user chooses to force close the Gallery app, when entering the Camera app again, the user will be prompted with the following error message: "Can't connect to the camera". Please, see the attached screenshot for more info.
Setting the light exposure to 4 or -4, the icon on the bottom right doesn't show any number (as it does for any other value) and if slide to the left to enter the Gallery and come back to camera app, the icon appears distorted. This happens only for value "4" or "-4". Workaround: switch to any of the other values and then back to 4.
Please, see the attached screenshot for more info.
Zooming in/out doesn't work in video mode. Nothing happens when using two fingers to zoom in or out. No change in the actual image.
Please, see the log below for zooming issue.
Code:
E/QualcommCameraHardware(148): Failed to get maximum zoom value...setting max zoom to zero
2. Text cut off in photo editor (To be confirmed in Beta 4)
The text for the "straighten" option is missing the first 2-3 letters in the default photo editor (please, see the attached screenshot for more info). The options section from that screen cannot be slid more to the left to see the rest of the word.
This happens most likely because the spaces between the icons (options) from the top row of editing options don't adjust to the new screen orientation (Portrait). They look ok in Landscape mode, but it seems that the space between the icons from that row is kept the same no matter of the screen orientation, leading to some of the options not to be completely visible.
3. cLock widget not properly resizing in landscape mode (To be confirmed in Beta 4)
cLock widget does not properly resize when the launcher is set to Landscape mode (launcher auto-rotate option is ON). The widget is cut off (please, see the attached screenshot for more info). The widget looks good in Portrait mode. But when turning the screen to landscape mode, it's cut.
4. Phone encryption (To be confirmed in Beta 4)
Enabling encryption in the Security Settings will make the PIN code for the SIM card (assuming it's set to be requested) not to be requested anymore, thus making the "phone" part of the device unusable. No calls (voice or data), no SMS, no MMS can be sent or received. Workaround: make a nandroid backup before encrypting and restore it afterwards.
If the user turns off the SIM card PIN code request before performing the encryption, after it's finished, the APNs previously set will disappear and there won't be any way to re-add them manually, thus making the data connection unusable. He will be able to make voice calls and send SMS though.
After the encryption, if SIM PIN request is OFF, in the notification drawer and quicksettings panel, the user will be informed that he has no service (please, see the attached screenshots for more info) although, by going into Settings -> About Phone -> Status, he will see that the network is successfully recognized and there is definitely some service. (please, see the attached screenshot for more info on this too).
5. Random reboots after recently closing a phone call (To be confirmed in Beta 4)
From time to time, but apparently more often after recently (not immediately after) closing an incoming voice call, the phone reboots.
This does not happen with kernel 3.4.56 but it does happen with 3.4.57 so it might be because of that reverted commit.
6. Some third party camera apps don't work properly in CyanogenMod. (To be confirmed in Beta 4)
Some third party camera apps don't work with any CM version from CM9 to CM10.1. For example, Camera 360 Ultimate v4.5 works ok on stock Android 4.1.2 and 4.2.2 (tested on Nexus devices) but doesn't work properly with any CyanogenMod version. After taking a picture, the camera preview gets stuck. No change in preview when tilting the phone.
Please, see the log below from the moment when taking a picture with Camera 360. Maybe it helps solve this problem.
Code:
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.getParentParam(EffectInfoFactory.java:1433)
W/System.err( 2142): at vStudio.Android.Camera360.photo.EffectInfoFactory.search(EffectInfoFactory.java:1303)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeAbstract.setEffect(ModeAbstract.java:106)
W/System.err( 2142): at vStudio.Android.Camera360.camera.logics.ModeNormal.onCameraStartPreview(ModeNormal.java:370)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraBaseActivity.onCreate(CameraBaseActivity.java:749)
W/System.err( 2142): at vStudio.Android.Camera360.camera.CameraMain.onCreate(CameraMain.java:551)
V/QualcommCameraHardware( 143): As Auto Focus is not in progress, Cancel Auto Focus is ignored
V/QualcommCameraHardware( 143): cancelAutoFocusInternal X: 0
I/QualcommCameraHardware( 143): stopPreviewInternal X: 0
V/QualcommCameraHardware( 143): initRawSnapshot E
I/QualcommCameraHardware( 143): runframethread: waiting for preview thread to complete.
V/QualcommCameraHardware( 143): initRawSnapshot X
V/QualcommCameraHardware( 143): takePicture: X
I/ShotSingle( 143): ShotSingle::takePicture end
I/CameraHAL( 143): camera_take_picture--- rv 0
I/QualcommCameraHardware( 143): initPreview: old preview thread completed.
QualcommCameraHardware( 143): destroying MemPool record
camera_set_preview_window---: window is NULL
V/QualcommCameraHardware( 143): Overlay object NULL. returning
I/CameraClient( 143): Destroying camera 0
I/CameraHAL( 143): camera_device_close+++: device 0x1f68650
I/SecCameraHardwareInterface( 143): SecCameraHardwareInterface destroyed: pid=143
I/ShotSingle( 143): ShotSingle destroyed: pid=143
I/ShotCommon( 143): ShotCommon destroyed: pid=143
No JNI_OnLoad found in /data/app-lib/vStudio.Android.Camera360-1/libmp3lame.so
I/ActivityManager( 430): Process vStudio.Android.Camera360 (pid 2142) has died.
7. USB tethering does not work
8. USB OTG does not work. (To be confirmed in Beta 4)
XDA:DevDB Information
CyanogenMod 10.1 - Beta 4 - Discussion thread / Bug report, ROM for the Samsung Galaxy W I8150
Contributors
arsradu
ROM OS Version: 4.2.x Jelly Bean
Version Information
Status: Testing
Created 2013-09-29
Last Updated 2014-05-19

charge
Opening off the phone while charging for no reason
sorry my bad english:angel:
I got help from google translate:victory:

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks
-Sent from 4.2.2 powered i8150-

hotheabilly said:
Why blackcat using old xistance kernel? And is he'd using latest bcmdhd wifi driver by arco or just old one? Thanks
-Sent from 4.2.2 powered i8150-
Click to expand...
Click to collapse
arco new bcmdhd wifi driver dont working

The phone had been rebooting often.
Happened occasionally it rebooted even using camera and browsing the net.

I installed this rom. But sometimes, phone is locking and freezing. I am obliged to reboot.
(Sorry for my bad English)

Please rename this rom.
I'm writing this post because I read the whole thread in the Development section and it seems to me that calling this rom CM 10.1 is a bit misleading.
Sure blackcat67 may have done a bunch of work to get this out, but I don't think he has the rights to call it CM.
So I'm asking @blackcat67...PLEASE RENAME YOUR ROM.
Call it something like... [4.2.2][Blackcat]...as Xistance did for his... [4.2.1][Rootbox Alpha 1] ...but please don't call it CyanogenMod.

arsradu said:
Opening this thread in order for the people to post their issues here instead of the development section or CM10 bug report thread.
This thread refers to discussions/bug reports for CyanogenMod 10.1 posted today by blackcat67 here.
As usual it would be best to keep an organized fashion of your bug reports for the developers to easily spot them and maybe fix them.
For that, please, copy-paste this in your posts, editing it accordingly:
HTML:
[B]Version:[/B] CM10.1 - Alpha 1
[B]App/Game/Subject:[/B] WRITE HERE APPNAME
[B]Bug title:[/B] WRITE HERE BUG TITLE
[B]Description:[/B] WRITE HERE BUG DESCRIPTION
Click to expand...
Click to collapse
I Will wait for Arco's or Camcory's version:crying:

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Bernedeboi said:
I Will wait for Arco's or Camcory's version:crying:
Click to expand...
Click to collapse
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app

ipromeh said:
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I don't know, man.
I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.

Re: CyanogenMod 10.1 - Discussion thread / Bug report
arsradu said:
I don't know, man.
I would keep it open just in case someone will post another CM10.1.
There is no source thread to discuss for now, that's true. But maybe there will be soon. So, I don't know. I'll leave this decision to mods.
From my point of view, I just want a CM10.1/AOSP 4.2.2 soon, and it's not really important who posts it. So...I don't know. You decide.
Click to expand...
Click to collapse
Everybody want that, just patiently waiting. . .
-Sent from 4.2.2 powered i8150-

ipromeh said:
Do we need to close this thread?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
no, we don't have to closed this thread, The Real Devs will post their CM10.1 someday,
we just need to be patient

Re: CyanogenMod 10.1 - Discussion thread / Bug report
arsradu said:
Version: CM10.1 - Alpha 1
Click to expand...
Click to collapse
Hmmm.... How about deleting the CM10.1 version, other users would think that there IS a CM10.1 ROM for the W but its already deleted...
Ehndroix JB with S3 Style Pack :thumbup:

TiTAN-O-One said:
Hmmm.... How about deleting the CM10.1 version, other users would think that there IS a CM10.1 ROM for the W but its already deleted...
Ehndroix JB with S3 Style Pack :thumbup:
Click to expand...
Click to collapse
OK. I edited the OP so that it doesn't contain any link or info related to that post.

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Its time reopen this thread.
Arco has just released CM10.1
Sent from my GT-I8150 using xda premium

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Now we can continue to discuss about cm10.1 here
Sent from my GT-I8150 using xda premium

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Welcome guys to CM10.1 *unbelievable happy face*
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
I'll do a Pristine Flash tomorrow and report here.

Re: CyanogenMod 10.1 - Discussion thread / Bug report
Me too. Feel very happy and excited. I dont know how to express my happiness. Sir is really amazing. Thanks sir
Sent from my GT-I8150 using xda premium

I will flash it now :fingers-crossed:
downloaded
Edit: flashed , it is the smoothest rom ever ... It is the best from the best developer

fo the swap go here
http://forum.xda-developers.com/showpost.php?p=39749848&postcount=22

myONEv RC9.5 FX+ HtcPhotoEnhancer.apk Runtime Error

Hi there!
first I would like to say that I absolutely love this ROM and have a deep respect for the developer, ckpv5. I have ran antutu benchmark on almost al PrimoU Roms available and this ROM w has the highest score of 7930!! I love the stability and speed. In adb or ddms there almost no errors. The only bug I found was that HtcPhotoEnhancer.apk forcecloses when opened from the htc gallery app. I understand development for this ROM is discontinued because it's flawless. So I tried to fix my self.
ADB logcat gives this error when opening PhotoEnhancer:
Code:
D/com.htc.photoenhancer.PhotoEffects(20687): ThumbnailThread: Apply effect_Thumbnail 1 end
D/com.htc.photoenhancer.PhotoEffects(20687): RenderThumbnailAllPreset: Apply effect_Thumbnail 2 start
D/com.htc.photoenhancer.PhotoEffects(20687): Preset Name: Helios
D/com.htc.photoenhancer.PhotoEffects(20687): Rect w=479, h=479
W/System.err(20687): JNI-Native library already loaded
I/Adreno200-EGLSUB( 1576): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 1576): <GetImageAttributes:1102>: RGBA_8888
W/System.err(20687): JNI-Native library already loaded
W/dalvikvm(20687): threadid=11: thread exiting with uncaught exception (group=0x40afd228)
E/EmbeddedLogger( 2671): App crashed! Process: com.htc.photoenhancer
E/EmbeddedLogger( 2671): App crashed! Package: com.htc.photoenhancer v108353154 (1.1.2222201912.466267.375952)
E/EmbeddedLogger( 2671): Application Label: Photo Enhancer
E/AndroidRuntime(20687): FATAL EXCEPTION: Thread-1956
E/AndroidRuntime(20687): java.lang.IllegalArgumentException
E/AndroidRuntime(20687): at com.scalado.caps.filter.clearshot.Exposure.set(Exposure.java)
E/AndroidRuntime(20687): at com.htc.photoenhancer.PhotoEffects$ExposureEffect.applyeffect(PhotoEffects.java)
E/AndroidRuntime(20687): at com.htc.photoenhancer.PhotoEffects.DoEffect(PhotoEffects.java)
E/AndroidRuntime(20687): at com.htc.photoenhancer.PhotoEffects.access$2700(PhotoEffects.java)
E/AndroidRuntime(20687): at com.htc.photoenhancer.PhotoEffects$ThumbnailThread.run(PhotoEffects.java)
W/ActivityManager( 2671): Force finishing activity com.htc.photoenhancer/.PhotoEnhancer
I decompiled HtcPhotoEnhancer.apk using apktool and went to HtcPhotoEnhancer/smali/com/scalado/caps/filter/clearshot/Exposure.smali and opened it with gedit(Im using ubuntu). I believe i now have the sourcecode where the error happens but I dot know how to look for it Because this Rom is no longer supported by the developer I thougt to ask the community for help and hope that we together can find an solution for this problem! Not that this is a big issue, the rom is AWSOME! I just want to learn how to fix runtime errors using adb and in the end help the One V community
regards LQi

Im using the same rom but i dont get any error in photo enhancer.
Sent from my HTC One V using xda app-developers app

Have you tried to clean your dalvik cache? I used this rom too and had not problems with it.

readinglamp said:
Have you tried to clean your dalvik cache? I used this rom too and had not problems with it.
Click to expand...
Click to collapse
I have and it also happens to me on RC3.5
Verstuurd vanaf mijn HTC One V met Tapatalk 4

Maybe you can delete your thumbnails and let they be created again. Or you could copy your photos to your computer, delete them from the phone and try to copy them back one by one. I don't think it is a general error, I think some of your photos/thumbnails are corrupted.

Thanks will try that and report back!

[MAGISK] OnePlus Analytics Disabler

It was recently discovered that OnePlus uses some over the top analytics that you can't opt out of. I'm not going to get into details as I'm not a developer, but you can read more at the link at the bottom of this post. I made a quick Magisk module that disables the tracking app by replacing it and it's odex file with an empty one, the standard procedure for disabling apps with Magisk. It should work on any OnePlus phone that uses this tracking app.
Install this through Magisk Manager.
More info:
https://www.chrisdcmoore.co.uk/post/oneplus-analytics/
Edit: I'm seeing a few cases of module not working for some people. I'm not certain what's causing it, but please make sure you're using the official rom and the beta version of Magisk. I'll continue looking into the errors while I'm not working.
UPDATE: Now replaces OPDeviceManager and OPDeviceManagerProvider, thanks to @WhoDunnit for bringing it to my attention. I still haven't been able to replicate any errors or find anything to fix them. Hopefully OnePlus pulls through and disables the tracking so this mod isn't needed.
Update 2: As long as I'm dragging behind, I'll just keep linking to WhoDunnit's modules within this thread. His updated module includes my changes but only disables the EngineeringMode backdoor, rather than the entire app, as well as disabling OPBugReportLite. Any updates I personally make will be based off this module, but hopefully we won't need any more. Here's the post with the updated module: https://forum.xda-developers.com/on...plus-analytics-disabler-t3686636/post74614087
Version 1.2: now disables EngineeringMode and related files.
PrivacyFix 1.0 disables OPDeviceManager.apk, OPDeviceManagerProvider.apk, libdoor.so (Engineering backdoor), OEMLogKit.apk, LogKitSdService.apk, oemlogkit, OPBugReportLite.apk. Remember to remove my old module.

very smart of you to make this. Im sure this will also benefit battery life as well not logging and shipping all of our information and activities at a whim.

Thx :highfive:

Very cool OP, thanks very much!

What am I doing wrong? I tried going to Modules, then tapping the + icon. When selecting this mod, I get the following screen
{
"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"
}
Sent from my ONEPLUS A5000 using Tapatalk

This work with any OOS phone such as OnePlus 2 and 3?
Sent from my OnePlus 3 using XDA Labs

Will this work after a software update, or do we need to run every time?

Devhux said:
What am I doing wrong? I tried going to Modules, then tapping the + icon. When selecting this mod, I get the following screen
Click to expand...
Click to collapse
That's interesting. I can't find any information on that error and it seems to only be you. Try deleting the zip and redownloading it. If that fails, you can try flashing it though recovery, but I haven't tested this method. Still, no reason to think it won't work.
Are you using the latest Magisk beta?
mrmcshagbag said:
This work with any OOS phone such as OnePlus 2 and 3?
Click to expand...
Click to collapse
It should work as long as the APK name doesn't change. No reason it should change, as it's a generic name. I don't know if other devices use it though. Worst case scenario you get a fake app taking up 0 bytes of precious storage.
GroovyGeek said:
Will this work after a software update, or do we need to run every time?
Click to expand...
Click to collapse
If Magisk gets removed by a system update then you'll have to reinstall Magisk to get the module working again. You won't have to reinstall the module.

Blame Tapatalk. I'm seriously looking to throw this app out the window as it's being stupid lately.
Sent from my ONEPLUS A5000 using Tapatalk

Just flashed it on my 3t running oos 4.5.0, is there a way to verify its working as I have become very paranoid with this revelation. I am finally and seriously considering to stop using oos, even though I haven't used a custom rom yet on my 3t.

Thanks.

Is this only for stock OOS?

My Magisk Manager crashed every time installing this module. Here are the logs:
Process: com.topjohnwu.magisk
Flags: 0x38c8be44
Package: com.topjohnwu.magisk v51 (5.1.1)
Foreground: Yes
Build: OnePlus/OnePlus3/OnePlus3T:7.1.1/NMF26F/09151130:user/release-keys
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.lang.ref.WeakReference.get()' on a null object reference
at com.topjohnwu.magisk.a.i.f(Unknown Source)
at com.topjohnwu.magisk.a.b.a(Unknown Source)
at com.topjohnwu.magisk.a.b.onPostExecute(Unknown Source)
at android.os.AsyncTask.finish(AsyncTask.java:667)
at android.os.AsyncTask.-wrap1(AsyncTask.java)
at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:684)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6374)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)
Click to expand...
Click to collapse
Logcat:
10-11 11:29:36.075 11175 11175 E AndroidRuntime: FATAL EXCEPTION: main
10-11 11:29:36.075 11175 11175 E AndroidRuntime: Process: com.topjohnwu.magisk, PID: 11175
10-11 11:29:36.075 11175 11175 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.lang.ref.WeakReference.get()' on a null object reference
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at com.topjohnwu.magisk.a.i.f(Unknown Source)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at com.topjohnwu.magisk.a.b.a(Unknown Source)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at com.topjohnwu.magisk.a.b.onPostExecute(Unknown Source)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:667)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at android.os.AsyncTask.-wrap1(AsyncTask.java)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:684)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6374)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
10-11 11:29:36.075 11175 11175 E AndroidRuntime: at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:103)
10-11 11:29:36.097 4365 15869 W ActivityManager: Force finishing activity com.topjohnwu.magisk/.FlashActivity
Click to expand...
Click to collapse

A simple question. I apologize for my ignorance...
Why do you not simply remove the OPDeviceManager from /system/priv-app instead of make a Magisk module for that?
benwalburn said:
It was recently discovered that OnePlus uses some over the top analytics that you can't opt out of. I'm not going to get into details as I'm not a developer, but you can read more at the link at the bottom of this post. I made a quick Magisk module that disables the tracking app by replacing it and it's odex file with an empty one, the standard procedure for disabling apps with Magisk. It should work on any OnePlus phone that uses this tracking app.
Install this through Magisk Manager.
More info:
https://www.chrisdcmoore.co.uk/post/oneplus-analytics/
Click to expand...
Click to collapse

Thank you! Two of my devices are now safe

Devhux said:
What am I doing wrong? I tried going to Modules, then tapping the + icon. When selecting this mod, I get the following screen View attachment 4298993
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Put this file in folder "MagiskManager" and then try again.
Wysłane z mojego ONEPLUS A5000 przy użyciu Tapatalka

It can use for 1+3t ?

Hello !! I tried to install this with magisk, but i don't know if it's good or not. I'm on the xXx's rom, and never used magisk before.
At the end of the installation, i've installation failed, Can you tell me why please ? Thanks you.

B.Z.H.29 said:
Hello !! I tried to install this with magisk, but i don't know if it's good or not. I'm on the xXx's rom, and never used magisk before.
At the end of the installation, i've installation failed, Can you tell me why please ? Thanks you.
Click to expand...
Click to collapse
This is for OOS and nothing else, and is not needed on custom ROMs.
Gesendet von meinem ONEPLUS A5000 mit Tapatalk

64ashg said:
Just flashed it on my 3t running oos 4.5.0, is there a way to verify its working as I have become very paranoid with this revelation. I am finally and seriously considering to stop using oos, even though I haven't used a custom rom yet on my 3t.
Click to expand...
Click to collapse
Yeah, just open Settings > Apps > overflow button > show System apps > and see if OPDeviceManager is there. Since I replaced it with an invalid app, you shouldn't see it in the apps at all.
yehyeh said:
My Magisk Manager crashed every time installing this module. Here are the logs:
Logcat:
Click to expand...
Click to collapse
I wasn't able to replicate the issue on Magisk 14.2. Are you still on the stable release? In spite of the name, the stable is broken. Aside from that, it should work. The way the module is designed it should install on any phone with a properly functioning Magisk, even if the app I'm disabling doesn't exist.
bartito said:
A simple question. I apologize for my ignorance...
Why do you not simply remove the OPDeviceManager from /system/priv-app instead of make a Magisk module for that?
Click to expand...
Click to collapse
Because Magisk modules are all the rage. But seriously, people don't like messing with /system anymore. Just like any other module, this allows you to modify the system without actually modifying it. It shouldn't trip SafetyNet and the module can be reapplied after an update by simply reinstalling Magisk. The change itself can be disabled with a checkbox, which I think is great for people who don't want to get their hands dirty, or for testing bugs. It's better in the long term for users of otherwise stock ROMs.
I did hear after making this module that you can disable the app with ADB, which is a roughly equal solution. I'd still prefer this just for the ability to manage it through Magisk. Being able to see the changes you've made to your phone just by glancing at an app is pretty useful.