Related
·:*¨¨*:·..·:*¨☆007☆·:*¨¨*:·..·:*¨
straight from The Land of Smiles
Jame Bond kernels have always been about battery efficiency without sacrificing speed...
-latest version-v3.7.1
☆★☆★☆
-linaro gcc
-some debugging disabled
-undervolted
-interactive governor (default) is recommended
-GPU set to 307MHz
-boots to 1.2 (oc to 1.3)
-cm color control
-eze sound control
-imoseyon gamma control
-installation/Tweaks (colors)
Click to expand...
Click to collapse
-uv settings
Click to expand...
Click to collapse
-protips
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
note: please "rate" the thread
Thank you to those that have! If you are new to this thread, browse through the pages. I always try to answer questions quickly and thoroughly, as well as provide a stable kernel. If this kernel doesn't have the "features" you are looking for, or you have seen a cool new mod, just ask and I will try to accommodate (or at least give a reason why not)
thanks for your time -og
acronyms, notes, etc.
deprecated kernels
***************************************************************************************************************************************
4.2.x kernel(s)
1.2/3.5GHz◊GPU 307MHz
☆007☆ v3.7.1
Click to expand...
Click to collapse
4.1.x kernel(s)
that thae
1.2/3.5GHz◊GPU 307MHz
☆Jame Bond☆ v3.4
1.2/3.5GHz◊GPU 307MHz
☆Jame Bond☆ v3.3
mirror
khlang
1.2/3.5GHz◊GPU 307MHz
☆Jame Bond☆ v3.4.6
Click to expand...
Click to collapse
_____________________________________________________________________
thanks to coolbho3000 for his patches
support setcpu
» kernel source
» additional source
Control your Android phone's CPU! SetCPU for Root Users
installation
2 ways...
-download and extract boot.img from zip...non-ak versions
-enter fastboot mode by (with phone off) press and hold volume up&down and then power
then to test (reverts on reboot)
Code:
fastboot boot boot.img
to flash
Code:
fastboot flash boot boot.img
or
-download to sd card and flash from recovery
tweaks
version 3.7.x has several "tweaks" that are controlled in system/etc/init.d/007tweaks
-color control
-gamma control
-volume boost
-high performance sound
everything boots to stock settings
included is system/etc/init.d/007tweaks.bkk which are my preferred settings (just rename to 007tweaks)
also can be adjusted with (most likely not colors) GLaDOS Control and Trinity Kernel Toolbox (as well as other kernel apps)
007tweaks
Code:
#!/system/bin/sh
echo "0" > /sys/class/misc/samoled_color/red_v1_offset
echo "0" > /sys/class/misc/samoled_color/green_v1_offset
echo "0" > /sys/class/misc/samoled_color/blue_v1_offset
#default 0 0 0
echo "1670000000" > /sys/class/misc/samoled_color/red_multiplier
echo "1880000000" > /sys/class/misc/samoled_color/green_multiplier
echo "2000000000" > /sys/class/misc/samoled_color/blue_multiplier
#default 2004318071 2004318071 2004318071
mount -o remount,noauto_da_alloc /data /data
echo "0" > /sys/devices/platform/omapdss/manager0/gamma
#default 5 off 0 max 10 (10 being darkest)
echo "2" > /sys/class/misc/soundcontrol/volume_boost
#default 0 max 3
echo "0" > /sys/class/misc/soundcontrol/highperf_enabled
#default 0
permissions are set on flashing, but if changed with "es explorer" they need to be reset to
for roms that don't have "color slider adjustments" to have the changes take affect without rebooting, open a terminal and run....
Code:
su <enter>
run-parts /etc/init.d/ <enter>
kernels are preset
don't drop more than 75mV under default
protips-
force desktop mode on google chrome
create the file /data/local/chrome-command-line and add below
Code:
adb shell 'echo \"chrome --user-agent="[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.45 Safari/535.19]"\" > /data/local/chrome-command-line'
Click to expand...
Click to collapse
[GUIDE] Proper FULL wipe
Click to expand...
Click to collapse
Tutorial: How to properly post a bug
Click to expand...
Click to collapse
galaxy nexus factory images
Click to expand...
Click to collapse
VLC player for android
Click to expand...
Click to collapse
https://plus.google.com/u/0/101056148805473200158/posts/SsowCdLfTPn
Click to expand...
Click to collapse
-for better scrolling in apps (specifically twitter) go to settings/developer options and select "Force GPU rendering"
*may crash other non-ics optimized apps(twiiter updated for ics)
Click to expand...
Click to collapse
-cool recovery trick to get rid of all the extra "no's" (recovery)
Code:
adb shell
touch /sdcard/clockworkmod/.one_confirm
Click to expand...
Click to collapse
-md5 mismatch (recovery)
Code:
adb shell
cd /sdcard/clockworkmod/backup/2011-11-29.18.20.30
rm nandroid.md5
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
enable 3g video chat (easiest way)
download this from market
Click to expand...
Click to collapse
battery saving tips-
disable gps unless navigating
don't use active widgets that need data
use 2g in low 3g signal areas
2g uses the least power
wifi uses less power than 3g
4g uses the most power, avoid when possible
Click to expand...
Click to collapse
great standby
overnight deep sleep (gsm)(ics)
more to come...
Omg happy to see you. Getting all the Samsung all stars here.
Sent from my Galaxy Nexus using XDA App
Can work with ARHD 2.1.2?
siewsphone said:
Can work with ARHD 2.1.2?
Click to expand...
Click to collapse
Shoult work! ARHD is 4.0.2! Try it out!
Im try it:
fastboot boot boot.img
But Device need to boot cca. 10-15 minutes. also Boot animation(THIS one) is very slow.
Does it have gpu oc?
Sent from my Galaxy Nexus using XDA App
anyone know why my phone need 1325mV for 350Mhz to work?
My settings:
350 / 1325mV
700 / 1175mV
920 / 1200mV
1200 / 1200mV
1400 / 1250mV
OTG
does it support OTG?
Great to see you in this forum mate. I loved your Kernel for the SGSII. I will be definately flashing it when AOSP pushes 4.0.3 properly.
tested on ARHD 2.1.2 and works fine
great job ogdobber
Nice to see a 4.0.2 kernel, thought we were forgotten.
Would you post an Anykernel version with just the kernel.
Thanks
Muchly appreciated! +1 to seeing a 4.0.2 kernel..
All running smooth as silk so far...
Kraenesk said:
Does it have gpu oc?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
yes the gpu is set to 384
siewsphone said:
anyone know why my phone need 1325mV for 350Mhz to work?
My settings:
350 / 1325mV
700 / 1175mV
920 / 1200mV
1200 / 1200mV
1400 / 1250mV
Click to expand...
Click to collapse
those settings look way off check post 3
ymr0211 said:
does it support OTG?
Click to expand...
Click to collapse
yes, but not usb storage. I forgot all about that. I have been using chainfires stickmount app. It does support keyboard and mouse though.
Gingernut78 said:
Nice to see a 4.0.2 kernel, thought we were forgotten.
Would you post an Anykernel version with just the kernel.
Thanks
Click to expand...
Click to collapse
I will upload it shortly
Cool, thanks for the anykernel version. Didn't want to flash the boot.img as it will overwrite the tweaked boot.img from ARHD 2.1.2.
When I clock down the CPU to 1200, will the 384 for GPU will stay?
Originally Posted by ogdobber
yes i can tell you I hate the naming game...and I'm not good at it
v.1.x.x kernels are basically stock kernels with undervolting and overclocking ability
v2.1 are nd kernel variations
v.2.2.x are fs version...
v2.3.x ndsf
v2.4.x socfs
vX= major change
vx.X=minor change
vx.x.X=variation of that version
I still need to cleanup as long as you can read this line...
meaning there are currently socfs kernels that are 2.3.x ans ndfs that are 2.2.x
I admit , its a mess, but i will get it organized
Click to expand...
Click to collapse
acronyms explained
ND=non-debug
fs=fsync disabled
ndfs=add the ^above
socfs= it is a ndfs building with a different config
cc= color control
fc= fast charge (usb)
mv= morfic vibration
ak= any kernel. keeps original ramdisk(all roms)
up2u=kernel will boot to stock voltages (must be user set)
*not all phones will be able to run 1.4GHz
-ND and fs kernels will see a significant battery savings in standby
Will the Kernel boot @ standard voltages or is he already undervolted, when yes, can you post standard voltages, thanks!
{
"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"
}
Preamble
This is the development thread for HTC Wildfire S and msm7227 devices. If you have questions about the code of the ROM and want to discuss changes and stuff we have developed feel free to ask here.
I've been working on a CM9 port for the HTC Wildfire S since January 2012 and started with CM10 in August 2012. After 5 month of work this I've released the first ALPHA of CM9. Getting CM10 was esier. Neither CM10 is stable yet nor the HTC Wildfire S (Marvel) port is complete. Most of the features are working but it still needs bugfixing and polishing. We would like to improve the code and get as much as possible upstream if they accept it. There will never be an official CM10 release as ARMv6 is not supported.
I have to thank alquez who ported CM7 for the HTC Wildfire S. His work was a good starting point for CM9 and then CM10. Also thanks to Tobias Droste who was working with me on this ROM. Tobias we finally made it!
I also have to thank WinSuk and s0be working on CM9 and CM10 for the Liberty. We worked together with those guys to get CM9 and CM10 going. We will continue our collaboration in future.
Reporting Bugs
If you want to report bugs please read THIS HOWTO first. Please try to provide logs if you see errors (logcat and dmesg). If you don't know how to do that check google or ask people here to help you. Don't contact me directly.
Enabling logcat Logging
adb shell dmesg
How to use strace?
All bug reports should go to the bugtracker.
If you think you find a bug take a look at the bugtracker first. Check if it already has been reported.
Sources
You can find the source here: http://git.cryptomilk.org/
If you are a developer working on a msm7227 and want to collaborate, contact me directly.
When it will be released as an alpha?
I think, it must have a good version number
I know now the reason why there are random force closes. After I open apps they will run as background process. And if I reach the (boarder) (only 140mb ram free) the apps start to crash. The kernel thinks that it is better to force close the apps before going into an to high usage of ram.
I tried to run an auto ram manager but without luck.
Now I try the option in the Developer Settings to allow just three background processes.
Not sure why but I think its a kernel bug.
Gesendet von meinem HTC Wildfire S A510e mit Tapatalk
any idea how to fix this compile error?
Code:
target thumb C++: camera.marvel <= device/htc/marvel/libcamera/cameraHal.cpp
target StaticLib: libaudiopolicy_legacy (out/target/product/marvel/obj/STATIC_LIBRARIES/libaudiopolicy_legacy_intermediates/libaudiopolicy_legacy.a)
target thumb C++: gps.marvel <= hardware/qcom/gps/loc_api/libloc_api/loc_eng_xtra.cpp
target thumb C++: gps.marvel <= hardware/qcom/gps/loc_api/libloc_api/loc_eng_ni.cpp
device/htc/marvel/libcamera/cameraHal.cpp:40:27: error: ui/OverlayHtc.h: No such file or directory
target thumb C++: gps.marvel <= hardware/qcom/gps/loc_api/libloc_api/loc_eng_log.cpp
target thumb C++: gps.marvel <= hardware/qcom/gps/loc_api/libloc_api/loc_eng_cfg.cpp
target thumb C: gps.marvel <= hardware/qcom/gps/loc_api/libloc_api/gps.c
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: librpc <= hardware/msm7k/librpc/xdr.c
target thumb C: librpc <= hardware/msm7k/librpc/rpc.c
device/htc/marvel/libcamera/cameraHal.cpp: In function 'int camera_set_preview_window(camera_device*, preview_stream_ops*)':
device/htc/marvel/libcamera/cameraHal.cpp:693: error: invalid use of incomplete type 'struct android::Overlay'
device/htc/marvel/libcamera/CameraHardwareInterface.h:29: error: forward declaration of 'struct android::Overlay'
target thumb C: librpc <= hardware/msm7k/librpc/svc.c
target thumb C: librpc <= hardware/msm7k/librpc/clnt.c
make: *** [out/target/product/marvel/obj/SHARED_LIBRARIES/camera.marvel_intermediates/cameraHal.o] Error 1
make: *** Waiting for unfinished jobs....
target StaticLib: libc_nomalloc (out/target/product/marvel/obj/STATIC_LIBRARIES/libc_nomalloc_intermediates/libc_nomalloc.a)
I'm not a dev' but I can try to hepl, I'm a student in C and when I get this error : "error: forward declaration of 'struct android::Overlay" it's that I haven't or wrong write the struct...
eoghan2t7 said:
any idea how to fix this compile error?
Click to expand...
Click to collapse
Droste just added the NoOpOverlay to our codebase.
modpunk said:
Droste just added the NoOpOverlay to our codebase.
Click to expand...
Click to collapse
Lovely thanks
Sent from my Wildfire S using Tapatalk 2
modpunk said:
Droste just added the NoOpOverlay to our codebase.
Click to expand...
Click to collapse
I know i'm not a dev and probably shouldn't even ask, but I googled noop overlay and found only one post on it in the entire interwebz. And all it said was that someone had written one and it didn't speed up server speeds. So might someone have the time to explain what it is and what it does?
It is a UI overlay which does nothing. See the marvel device source code ...
If you're not a developer but know how to use a shell and want to help, I will open "Tasks" in the bugtracker. These are things which need to be investigated. You can help me and work on those tasks.
https://code.google.com/p/cm9-wildfire-s/issues/list?can=2&q=label:Type-Task
I will add new ones from time to time.
Although a complete noob in developing, i'm willing to help as well, if instructed how to do it so, after installing the rom (from your other thread), i tried to help with the "battery current" task.
However, no matter which frequency i try, the command always returns the result 0.
I know i'm typing it correct (and works) since, if plugged, returns value 805. However, unplugged, the result is always 0.
Thanks for the info, good to know. I thought it would show the value it uses. Looks like it is the charging value...
i tried to get kernel and partial wakelocks to catch what stops deepsleep. didnt used phone 22 min after unplugged from charge.
So these are statistics:
Kernel Wakelocks: (in 22 min)
21m8s : msm_serial_hs_dma
11sec : powermanagerservice
10sec : radio-interface
Partial Wakelocks :
10sec : ActivityManager-Launch
7min : audioout_1
process:
ksmd : 10 sec
alarms:
com.android.phone : wakes up 8 times
com.google.android.gsf: wakes up 4 times
android : wakes up 2 times
and others:
no data connection : 22 min
no or unknown signal : 22 min
awake : 22 min
@Modpunk
Good work, one question: how did you fix the webrtc compile errors and how did you allow both the chrome web engine and the other Javascript one to run together?
Sent from my HTC Wildfire S A510e using xda premium
benjamingwynn said:
@Modpunk
Good work, one question: how did you fix the webrtc compile errors and how did you allow both the chrome web engine and the other Javascript one to run together?
Sent from my HTC Wildfire S A510e using xda premium
Click to expand...
Click to collapse
Cm fixed the webrtc errors and the chrome and v8 engine are added to the boardconfig.mk so they both compile
Sent from my Wildfire S using Tapatalk 2
I think the webrtc patch is still in the patches directory.
baddboyy said:
i tried to get kernel and partial wakelocks to catch what stops deepsleep. didnt used phone 22 min after unplugged from charge.
So these are statistics:
Kernel Wakelocks: (in 22 min)
21m8s : msm_serial_hs_dma
11sec : powermanagerservice
10sec : radio-interface
Partial Wakelocks :
10sec : ActivityManager-Launch
7min : audioout_1
process:
ksmd : 10 sec
alarms:
com.android.phone : wakes up 8 times
com.google.android.gsf: wakes up 4 times
android : wakes up 2 times
and others:
no data connection : 22 min
no or unknown signal : 22 min
awake : 22 min
Click to expand...
Click to collapse
I've fixed some problems were rild couldn't access some kernel interfaces but it is still strange. It looks like some information from rild is wrong.
What you see in "others". Something thinks we are always without a signal and search for it, which is wrong.
@baddboyy
If you want to help. Fully charge your phone. Turn radio on and wifi off. Shut down the phone and remove the charger.
Then turn it back on, unlock the sim and don't touch it for 30 min. Then check BetterBatteryStats and tell me what you see.
I've fixed deep sleep. The 'msm_serial_hs_dma' kernel wakelock was the culprit. Our platform doesn't support quick switch-on/off of Bluetooth Module which can be disabled with an overlay.
i think that fix deserves a compile! thanks modpunk once again
{
"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
After initially sending my S3 to the samsung repair center for service on the battery charger port, I have no longer been able to get on the NV LTE network.
Here are some symptoms for diagnosis:
1) MSL code no longer works -
I/MSL_Checker(13449): Enter checkMSLCode
I/MSL_Checker(13449): success to write
D/MSL_Checker(13449): mServiceMessenger is not null. Doing.
I/MSL_Checker(13449): End checkMSLData
I/MSL_Checker(13449): error=0
I/MSL_Checker(13449): size of result : 13
I/MSL_Checker(13449): onCreate
I/MSL_Checker(13449): onCreate2
I/MSL_Checker(13449): hdata_edit
I/MSL_Checker(13449): Chameleon diag valuenull
I/MSL_Checker(13449): Chameleon Check value2false
I/MSL_Checker(13449): connect To Secphone service
I/MSL_Checker(13449): onCreate1
E/ActivityThread(13449): Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): android.app.ServiceConnectionLeaked: Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.connectToRilService(MSL_Checker.java)
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.onCreate(MSL_Checker.java)
2) Hardware version shows L710.00
3) RIL version in ##RTN# shows 0x01
4) Attached getprop list - pastebin.com/nkkqZJb9
5) Signal strength reports max values - D/STATUSBAR-NetworkController(13330): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -85 -40 -92 -45 5 99 2147483647 2147483647 2147483647 2147483647 cdma 0x400 level=4
6) LTE Setting app from the market returns this exception : W/ActivityManager(13235): Permission Denial: starting Intent { act=android.intent.action.MAIN cmp=com.android.settings/.RadioInfo } from ProcessRecord{41f1ee58 18023:com.ru426.android.lte_settingforgx/u0a119} (pid=18023, uid=10119) requires com.sec.android.app.factorymode.permission.KEYSTRING
7) W/FactoryTestApp(13781): WARNNING: java.io.IOException: Connection refused
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connectLocal(Native Method)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connect(LocalSocketImpl.java)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocket.connect(LocalSocket.java)
W/FactoryTestApp(13781): WARNNING: com.sec.factory.aporiented.FtClient$ConnectionThread.run(FtClient.java:206)
Seems like your OS got corrupted somehow. Try to ODIN a stock rom (pick whichever one, doesnt really matter) and check then.
Also try to update your PRL and profile as is right now
CNexus said:
Seems like your OS got corrupted somehow. Try to ODIN a stock rom (pick whichever one, doesnt really matter) and check then.
Also try to update your PRL and profile as is right now
Click to expand...
Click to collapse
I have tried several combinations of both, including formatting the /system partition in CWM just to make sure thigns get wiped. still no return of the MSL.
possibly an efs repartioning?
ijunes said:
I have tried several combinations of both, including formatting the /system partition in CWM just to make sure thigns get wiped. still no return of the MSL.
possibly an efs repartioning?
Click to expand...
Click to collapse
You have to downgrade to 4.1.1 to get your MSL. Once you get it you can master reset and re provision and you should be good to go
☆SoA: Son's of Android™☆
I like to break stuff!
so back on LJ7, got my MSL, which switched over to all 2s now... and my LTE is still not working. any other ideas?
It also appears that the LTE Rx only flex cable was slightly stripped during the repair. Do you think that could be the culprit?
{
"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"
}
Maybe or you have LTE disabled. Check on settings/more settings/mobile networks.
Sent from my SPH-L710
i had gone between the two back and forth, i remember a whole back it only picked up prl and profile via cdma, but LTE is enabled, and even sprint zone says its enabled, just not connected. Unable to get any BSR reporting info neither..
I went ahead and removed the attached antenna from the back, and so far it appears to not have affected any of the existing forms of reception i had earlier.
I will swap out with another antenna from another GS3 and confirm the issue..
Ordering a new one is going to cost around $20, but i'm certain samsung didnt install it correctly when replacing the PCB but am too afraid to call them out on it for fear of voiding the warranty...
interestingly enough, the new antenna as picutred seems to do nothing, and removing it from a working one doesnt appear to affect its service neither...
ijunes said:
After initially sending my S3 to the samsung repair center for service on the battery charger port, I have no longer been able to get on the NV LTE network.
Here are some symptoms for diagnosis:
1) MSL code no longer works -
I/MSL_Checker(13449): Enter checkMSLCode
I/MSL_Checker(13449): success to write
D/MSL_Checker(13449): mServiceMessenger is not null. Doing.
I/MSL_Checker(13449): End checkMSLData
I/MSL_Checker(13449): error=0
I/MSL_Checker(13449): size of result : 13
I/MSL_Checker(13449): onCreate
I/MSL_Checker(13449): onCreate2
I/MSL_Checker(13449): hdata_edit
I/MSL_Checker(13449): Chameleon diag valuenull
I/MSL_Checker(13449): Chameleon Check value2false
I/MSL_Checker(13449): connect To Secphone service
I/MSL_Checker(13449): onCreate1
E/ActivityThread(13449): Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): android.app.ServiceConnectionLeaked: Activity com.android.hiddenmenu.MSL_Checker has leaked ServiceConnection [email protected] that was originally bound here
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.connectToRilService(MSL_Checker.java)
E/ActivityThread(13449): at com.android.hiddenmenu.MSL_Checker.onCreate(MSL_Checker.java)
2) Hardware version shows L710.00
3) RIL version in ##RTN# shows 0x01
4) Attached getprop list - pastebin.com/nkkqZJb9
5) Signal strength reports max values - D/STATUSBAR-NetworkController(13330): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -85 -40 -92 -45 5 99 2147483647 2147483647 2147483647 2147483647 cdma 0x400 level=4
6) LTE Setting app from the market returns this exception : W/ActivityManager(13235): Permission Denial: starting Intent { act=android.intent.action.MAIN cmp=com.android.settings/.RadioInfo } from ProcessRecord{41f1ee58 18023:com.ru426.android.lte_settingforgx/u0a119} (pid=18023, uid=10119) requires com.sec.android.app.factorymode.permission.KEYSTRING
7) W/FactoryTestApp(13781): WARNNING: java.io.IOException: Connection refused
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connectLocal(Native Method)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocketImpl.connect(LocalSocketImpl.java)
W/FactoryTestApp(13781): WARNNING: android.net.LocalSocket.connect(LocalSocket.java)
W/FactoryTestApp(13781): WARNNING: com.sec.factory.aporiented.FtClient$ConnectionThread.run(FtClient.java:206)
Click to expand...
Click to collapse
Was there every a resolution to this,I'm having the exact same issue after a samsung repair
---------- Post added at 04:14 PM ---------- Previous post was at 03:45 PM ----------
Also , there have been reports of this on sprint forums as well,one member sent it back to Samsung and noticed and extra step on there logs saying changed something of the sort to changing iccd to 4g, not sure what it meant and not sure if it fixed the problem. Maybe it has something to do with the programming of the actual hardware piece that controls the lte not the antennae? I'm really not educated in any of this but am experiencing the same problem so maybe contributing what little i know may help fix it,is there a way to dumb and diagnostic of the lte card/hardware piece?
Hi all,
I'm hoping someone can help with a Android 10 Dasaita PX6 that has wifi and bluetooth issues. In only about 1 in every 10 start ups does the unit seem to even turn on wifi and BT. On the other 9 occasions it doesn't even let me switch on wifi manually and BT can neither find nor be found.
I've changed the BT settings from fsc-bw124 in the factory settings to every other option and none of them have a different result with most not connecting at all. I've updated MCU all the way up to 3.8 in increments with the files from Dasaita and I've moved from MAX to VIVID to HAL and no difference in performance. Though I have to say Hal just looks better that the others.
When it does connect it works without issue or interruption until powered off then its a lottery again.
Any help would be greatly appreciated
{
"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"
}
What has been identified from reading the forums and tried.
Dasaita and forums I've seen recommended using newer MCU and I updated from 3.6 up to newest 3.8 through each version in-between.
Also updated MAX10 to newest version then swapped to vivid then Hal.
Factory reset before Hal.
Tried different phones. Tried to pair from the settings menu not the bt apps.
Tried changing to all the BT modules in the factory settings.
The forums I've seen all look to be variations on these themes. If you can point in the right direction that would be awesome.
marchnz said:
What has been identified from reading the forums and tried.
Click to expand...
Click to collapse
Is there any resource for troubleshooting that I've missed or can I provide anything more?
Do you have your head unit's wifi bubble turned on? You can't run wifi and wifi bubble at the same time.
Yup that's off should have mentioned that in the troubleshooting that I've done.
If you have done software updates with no success then it stands to reason it's a hardware error. Check for loose connections on the bt/wifi board. Wiggle it around a little.
Hi. I have the the same problem... Work everything fine for half year... No is no way to turn WiFi on...
Hi, no unfortunately I still don't have a fix. Dasaita also told me to change to the Bluetooth chip setting but that hasn't worked either. With out Bluetooth or wifi it's just a bad radio i was better off with the stock one.
Al_79 said:
Hi, no unfortunately I still don't have a fix. Dasaita also told me to change to the Bluetooth chip setting but that hasn't worked either. With out Bluetooth or wifi it's just a bad radio i was better off with the stock one.
Click to expand...
Click to collapse
Yes agree with you... Without these options this radio doesn't worst a that money.... I'm looking probably to sent it back, as my one still have a manufacture warranty
EGIS K said:
Yes agree with you... Without these options this radio doesn't worst a that money.... I'm looking probably to sent it back, as my one still have a manufacture warranty
Click to expand...
Click to collapse
Just another question is in what to change this one for Nissan X-Trail?
EGIS K said:
Just another question is in what to change this one for Nissan X-Trail?
Click to expand...
Click to collapse
Hi. I did sort my problem... I did pull out the radio, checked and reconnect the wiring.... Unplug power cable from stereo, plug it back.... Wi-Fi com on itself.... Now second day using stereo, and is no any problem so far... Maybe this helps for you as well...
Hi there,
Wondering if either of you @EGIS K or @Al_79 have managed to resolve the problem ?
(Im having the problem about ~30% of the times the wifi cant be turned on ( bluetooth is always working though). A simple reboot resolves the issue. I have a (1 week old) dasaita px6 running MTCH_HA_V3.80_1
Xoubir said:
Hi there,
Wondering if either of you @EGIS K or @Al_79 have managed to resolve the problem ?
(Im having the problem about ~30% of the times the wifi cant be turned on ( bluetooth is always working though). A simple reboot resolves the issue. I have a (1 week old) dasaita px6 running MTCH_HA_V3.80_1
Click to expand...
Click to collapse
Hi. I think i resolve my problem... I did update for the system and looks that the wi-fi stays on for all the time... I only nearly a week, after update, but looks it works so far...
Thanks @EGIS K for the update I'll post here if I make any progress
Xoubir said:
Thanks @EGIS K for the update I'll post here if I make any progress
Click to expand...
Click to collapse
New message from: dasaita-official-store-america (117
)
Hi there,
You can try to update the system: https://www.dropbox.com/s/z2cau61xdme5nbc/HA3_rk3399_10.0_ota(20220120)升级包.zip?dl=0
Download the file in an empty USB driver, connect to the radio and choose updating the system in settings.
EGIS K said:
New message from: dasaita-official-store-america (117
)
Hi there,
You can try to update the system: https://www.dropbox.com/s/z2cau61xdme5nbc/HA3_rk3399_10.0_ota(20220120)升级包.zip?dl=0
Download the file in an empty USB driver, connect to the radio and choose updating the system in settings.
Click to expand...
Click to collapse
This one done a job for me... So far everything works how it's should... After this update...
I thought I'd fixed it with an external USB Bluetooth and wifi dongle but after withing fine all day it's back to the same issue again.
marchnz said:
What has been identified from reading the forums and tried.
Click to expand...
Click to collapse
@marchnz I noticed on px5 threads there was a shell script that delayed wifi/bt initialisation to resolve a similar issue. Would you know if there is something like this floating around for the px6?
I think have isolated the corresponding errors for the wifi chip activation in the dmesg log file :
Error is that one (rtl88x2cs being the driver for the RTL8822CS wlan/bt chip) :
Code:
[ 845.098810] rtl88x2cs mmc0:0001:1: rtw_sdio_raw_write: sdio write failed (-110)
[ 845.098817] rtl88x2cs mmc0:0001:1: rtw_sdio: WRITE use CMD53
[ 845.098822] rtl88x2cs mmc0:0001:1: rtw_sdio: WRITE to 0x00014, 4 bytes
[ 845.098826] rtw_sdio: WRITE 00000000: 07 07 01 00
[ 845.098992] WARNING: CPU: 5 PID: 101 at drivers/net/wireless/rockchip_wlan/rtl8822cs/os_dep/linux/sdio_ops_linux.c:1329 rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.098995] Modules linked in: 8822cs aic8800_bsp
[ 845.099003] CPU: 5 PID: 101 Comm: kworker/5:2 Tainted: G W 4.19.111+ #271
[ 845.099006] Hardware name: Rockchip RK3399 HCT Board (DT)
[ 845.099014] Workqueue: events_freezable mmc_rescan
[ 845.099019] pstate: 60400005 (nZCv daif +PAN -UAO)
[ 845.099088] pc : rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.099158] lr : rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.099162] sp : ffffff800a92b7e0
[ 845.099165] x29: ffffff800a92b7e0 x28: <private info omitted>0
[ 845.099169] x27: <private info omitted>1 x26: ffffffc04489a000
[ 845.099174] x25: <private info omitted>0 x24: ffffffc07237f980
[ 845.099178] x23: <private info omitted>4 x22: ffffffc07237f980
[ 845.099182] x21: <private info omitted>4 x20: ffffffc022245800
[ 845.099187] x19: <private info omitted>4 x18: ffffffffffffffff
[ 845.099191] x17: <private info omitted>0 x16: <private info omitted>0
[ 845.099195] x15: ffffff800974da48 x14: ffffff8089908e6f
[ 845.099199] x13: ffffff8009908e7d x12: ffffff80099092ba
[ 845.099203] x11: ffffff800976e000 x10: 0000000005f5e0ff
[ 845.099208] x9 : 00000000ffffffd0 x8 : 2d2d2d2d2d2d2d2d
[ 845.099212] x7 : <private info omitted>0 x6 : 0000000000000fbe
[ 845.099216] x5 : <private info omitted>0 x4 : <private info omitted>0
[ 845.099221] x3 : ffffffffffffffff x2 : 4b5c3a83ba8c4f00
[ 845.099224] x1 : <private info omitted>0 x0 : <private info omitted>4
Corresponding kernel call stack :
Code:
[ 845.100519] Call trace:
[ 845.100588] rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[ 845.100656] sdio_io+0x88/0x138 [8822cs]
[ 845.100722] rtw_sdio_write_cmd53+0x14/0x1c [8822cs]
[ 845.100794] _halmac_sdio_reg_write_32+0x4c/0x68 [8822cs]
[ 845.100862] reg_w32_sdio_8822c+0x160/0x188 [8822cs]
[ 845.100930] mac_pwr_switch_sdio_8822c+0x200/0x2c4 [8822cs]
[ 845.101011] rtw_halmac_poweron+0x4c/0xd0 [8822cs]
[ 845.101086] rtl8822c_power_on+0x48/0x98 [8822cs]
[ 845.101165] rtw_hal_power_on+0x20/0x58 [8822cs]
[ 845.101243] rtw_hal_read_chip_info+0x44/0x90 [8822cs]
[ 845.101320] rtw_sdio_primary_adapter_init+0x110/0x15c [8822cs]
[ 845.101396] rtw_drv_init+0x8c/0x160 [8822cs]
[ 845.101407] sdio_bus_probe+0x108/0x130
[ 845.101420] really_probe+0x200/0x2b0
[ 845.101431] driver_probe_device+0x58/0x100
[ 845.101442] __device_attach_driver+0x90/0xc0
[ 845.101454] bus_for_each_drv+0x70/0xc8
[ 845.101465] __device_attach+0xdc/0x138
[ 845.101476] device_initial_probe+0x10/0x18
[ 845.101488] bus_probe_device+0x94/0xa0
[ 845.101499] device_add+0x428/0x6d8
[ 845.101507] sdio_add_func+0x60/0x88
[ 845.101511] mmc_attach_sdio+0x1b4/0x370
[ 845.101516] mmc_rescan+0x298/0x388
[ 845.101521] process_one_work+0x1a0/0x418
[ 845.101526] worker_thread+0x4c/0x3e0
[ 845.101530] kthread+0x12c/0x158
[ 845.101534] ret_from_fork+0x10/0x18
My specs : PX6 (Dasaita's MTCH)
Code:
[ 0.000000] Linux version 4.19.111+ ([email protected]) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) #271 SMP PREEMPT Sat Jan 8 17:33:05 CST 2022
[ 0.000000] Machine model: Rockchip RK3399 HCT Board
Not sure though if this points towards a software or hardware issue though :s