[Q&A] [ROM][UB][AOSP 4.4.4_r2 -V4.1] Sony Xperia P Android Open Source Xperia ROM - Sony Xperia P, U, Sola, Go

Q&A for [ROM][UB][AOSP 4.4.4_r2 -V4.1] Sony Xperia P Android Open Source Xperia ROM
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

help!!!
will not let me install the kernel, I do not start by flashtool and mobile me, I'm doing it from the stock rom ... I had installed the rom-Experience-V1 Sirius, you can install the rom AOSX-4.4.4_r2-nypon -V4.1 from Sirius? ... thanks for your help.

which rom between aosp and cm11 is more stable for daily use

jafa68 said:
will not let me install the kernel, I do not start by flashtool and mobile me, I'm doing it from the stock rom ... I had installed the rom-Experience-V1 Sirius, you can install the rom AOSX-4.4.4_r2-nypon -V4.1 from Sirius? ... thanks for your help.
Click to expand...
Click to collapse
Just do this:
Download the ROM
Extract boot.img and flash it
Copy the ROM to your SD Card
Boot into recovery
Wipe data, cache, dalvik cache
Install the ROM
Reboot
First post
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
tefl0n said:
which rom between aosp and cm11 is more stable for daily use
Click to expand...
Click to collapse
I use only AOSP 4.4.4_r2 -V4.1, and it's really comfortable and stable.
I don't know any trouble at this moment
I have been using it since release .

Keiichiart said:
I use only AOSP 4.4.4_r2 -V4.1, and it's really comfortable and stable.
I don't know any trouble at this moment
I have been using it since release .
Click to expand...
Click to collapse
I'm having some trouble pairing phone and car via blutooth with latest CM11 builds... do you know if this feature is working correctly in AOSP 4.4.4_r2 -V4.1?

Hi guys,
having probs with my xperia p .
unlocked the boorloader .
Flashed the boot.img with Flashtool like shown in this thread http://forum.xda-developers.com/showthread.php?t=1963961
the phone showed the logo and now the home button on the light bar is lit and the backlight of the screen is on.
no other response. Please advice
Keiichiart said:
Just do this:
Download the ROM
Extract boot.img and flash it
Copy the ROM to your SD Card
Boot into recovery
Wipe data, cache, dalvik cache
Install the ROM
Reboot
First post
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
Click to expand...
Click to collapse

Can't flash the rom.zip
@percy_g2 today i just tried to flash this rom and have some bragging rights 'bout my xperia p so i downloaded the rom,extracted boot.img from the .zip (I deleted the boot.img from the .zip then archived it again when i finished from flashing boot.img via fastboot),Then all of a sudden when i tried to flash the .zip to my phone thru cwm they told me status 7 installation aborted what should i do now?.
Actually my phone got soft bricked and now i fixed it again.

Xperia P won't Boot into recovery
Hello there, I'm a complete noob here, so please help me. thanks in advance.
I managed to unlock the bootloader, and did these :
1- Download the ROM
2- Extract boot.img and flash it
3- Copy the ROM to your SD Card
4- Boot into recovery.
Click to expand...
Click to collapse
but when I try to boot into recovery (pressing power key first, then pressing volme up key repeatedly), it shows the sony logo with "powered by aosx" logo in the end... after one second, it goes away and nothing happens..
I don't know what i did wrong and how can I make it right.
thanks.
Edit: I should have pressed power several times... figured it out... thanks.

First, thanks so much for the the ROM, glad I can update the sony 4.1 to some little more modern 4.4. Now, I have two newbie questions.
Can the ROM influence the GPS? In OSMAnd, I am now off by 50 metres from my actual location but it was working quite reliable on the old sony version. I'm a bit too lazy to install hundreds of different ROMs or to go back etc, so just checking if maybe someone has a thought?
Also I have a weird glitch with th gesture trail in the Google Keyboard, basically it doesn't forget the lines I have already drawn in the past on new words. I've attached a screenshot. The blue stuff there is *not* what I drew for this word, which was just a swipe left. Quite unusable
Thanks!
Amendment, apk from http://forum.xda-developers.com/android/apps-games/lollipop-keyboard-phones-root-t2910268 also has the same issue for me

Another issue, this app https://play.google.com/store/apps/details?id=de.rbb.sandmann installs and loads fine, but actually watching the videos doesn't work. logcat sadly is not very helpful....
Code:
+++ LOG: malformed log message
I/Unity (30104): play bubble : folge
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
I/Unity (30104): New camera mode : FilmeBubble
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
I/wpa_supplicant( 3595): wlan0: WPA: Group rekeying completed with [GTK=TKIP]
I/libblt_hw( 2846): Library opened (handle = 8, fd = 62)
I/libblt_hw( 2846): Library closed (handle = 10, fd = 51)
E/MediaPlayer(30104): pause called in state 1
E/MediaPlayer(30104): error (-38, 0) <--- here's the error
W/MediaPlayer(30104): mediaplayer went away with unhandled events
W/BufferQueue( 2846): [SurfaceView] cancelBuffer: BufferQueue has been abandoned!
I/libblt_hw( 2846): Library opened (handle = 9, fd = 51)
I/libblt_hw( 2846): Library closed (handle = 8, fd = 62)
I/Unity (30104): New camera mode : IntroEnd
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
I/Unity (30104):
I/Unity (30104):
I/Unity (30104): (Filename: ./artifacts/AndroidManagedGenerated/UnityEngineDebug.cpp Line: 49)
I/Unity (30104):
this works in stock rom. wonder if it could be missing some codecs etc?

Wifi with static ip
I just installed lastest version of this ROM: it seems great, but i have an issues with wifi: I need to connect with a static ip, but it doesn't work.
I did a wrong configuration of gateway: it works correctly now!

Can't boot, can't get into recovery with AOSX v4.1
Hey, your boot.img is probably corrupted. I flashed it after unlocking bootloader, but the device will never start. It freezes either at the screen with SONY logo and green robot, or afterwards it goes black (with backlight on) and hangs there. And no way to get into recovery - it won't react to volume keys
EDIT: Woops, it should've been the POWER BUTTON. mention this somewhere, please.

HTML5 video does not work; screen rotation faulty
I have noticed that HTML5 video does not work in any browser (tried stock, Opera and Firefox). Just video encoded with H264 for sure works with HW decoder in MX Player, but neither codec is supported in browsers for some reason. WebGL works in Firefox, but not in Opera or stock.
Another thing: screen auto-rotation mostly does not work. It works only in SatStat app from F-Droid repo for some reason. If an app for manual rotation is installed, you can switch it manually.

tefl0n said:
which rom between aosp and cm11 is more stable for daily use
Click to expand...
Click to collapse
aosp is more smooth than cm11 and doesn't have any extra features so its basically pure android, on the other hand cm11 is a tad bit slower but has alot of useful features
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
Venseiiz said:
Another thing: screen auto-rotation mostly does not work. It works only in SatStat app from F-Droid repo for some reason. If an app for manual rotation is installed, you can switch it manually.
Click to expand...
Click to collapse
Auto rotation will only work if auto brightness is turned on, this is for all kitkat and up versions of android for xperia p, I'm not sure as to why but thats how its always been.

Related

[ROM][CDMA]CM9 - Built for R800x - U:0605

FIRST OFF: THIS IS FOR UNLOCKED BOOTLOADERS. IF YOU TRY TO INSTALL THIS WITH A LOCKED BOOTLOADER, YOU WILL BRICK YOUR PHONE.
As aGraceful has been mentioning, Here is the CM9 thread dedicated to the R800x.
What it is:
We (myself, aGraceful or anybody else who's interested) will port FXP with every new release that comes out.
I (or if anybody else is interested) will be building & uploading a new version (from source) about mid-week (between FXP release) with the newest CM9 updates.
What it is not:
Neither myself, aGraceful, or anybody else who contributes claim any thing special about the code. Either FXP built it (if it's a port) or it's code from Cyangenmod/Koush/freexperia or anybody else who has contributed to the CM9/Android repos.
Starting 2012 June 06 -- I am using my own device tree and vendor tree to build this, so it should work better with wifi than FXP's builds.
Now, onto the good stuff.
What Works:
Data
Calls
Wifi
GPS
SMS
Accelerometer
MMS (thanks chrono!)
What Doesn't Work:
Bluetooth Media Audio (Thanks chrono!)
Video Recording (Thanks Neoandgeo for pointing that one out)
Facebook account syncing (Thanks DoubleByte) -- Note facebook account syncing looks like it's a problem within 4.0 framework...
Anything else that doesn't work, lemme know, I'll add it to the list.
FXP Changelog: changelog for fxp
Link to All Downloads
What's in it:
1) agraceful's port of FXP 115 116 117 (Current as of 04/22) I'm gonna stop hosting FXP ports through my mediafire, look to agraceful for those
2) mega_fix.zip -- contains Atarii's wifi/gamepad fix & 216monster's mms/carrier name fix
3) My latest build from source (newest date in the title)
4) Older builds
5) Copy of the libs I use for porting, If you're interested in trying to bring another ROM to our phone, these cover mostly everything) dev corner with some libs if you're interested in porting something.
Steps to do a install:
1) Download & copy to sdcard
2) reboot recovery,
3) MAKE A NANDROID!
4) wipe dalvik/cache
5) install from sdcard.
Steps to do a 100% clean install (we're talking if all else fails try this option)
1) Reboot into recovery, MAKE A NANDROID, wipe the 3 major things (data/cache/dalvik)
2) Turn off your phone & connect it in fastboot mode.
3) enter this fastboot erase system (this will erase the /system partition, insuring a clean install)
4) boot into recovery
5) install from zip.
Thanks to Ridder215215, a complete guide on how to install CM9 (just replace the link in line 2 with the link above)
As everybody knows, Flashing roms can lead to issues with your phone. When you decide to flash something, you are taking the responsibility for your phone working into your own hands.
Google apps: http://goo.im/gapps
or goo.im market app: https://play.google.com/store/apps/details?id=com.s0up.goomanager
Rom Update: 2012 April 11
1) Latest CM9 fixes.
2) Gamepad fix added in.
3) Wifi fix is included
4) Kernel is included in the zip this time, so no need to download two separate things
Test update: 2012 April 11
Uploaded a xLoud test version for y'all to try out. Please tell me how well it works for you guys! (If it makes a big enough difference, I'll change out dspmanager for it)
1) Added in xLoud framework (kinda, I think we're missing stuff from framework.jar/framework-res.apk so it doesn't show up in menu-> sound settings) ALSO: It's having an issue with wrong UID (settingsProvider.apk issue) so when I get around to it, i'll tear apart some things and see if it can't be ported.
2) Removed DSP manager
Kernel Update; 2012 April 14
Uploaded a new kernel for people to test out
Enabled governors:
Conservative
MinMax
SavagedZen
SmartAssv2
InteractiveX
Enabled IO Schedulers:
Anticipatory
Deadline
CFQ
V(R)
Disabled ALS (Thank Keiran)
Sources are FXP's (https://github.com/freexperia/semc-kernel-msm7x30-ics/tree/ics) All I did was tweak some minor stuff
Rom Update 2012 April 15
1) Latest CM Sources
2) No xLoud tweaks
3) Wifi fix built in (will be from now on)
4) Gamepad fix built in (will be from now on)
5) Set mmc to "12" in apns-conf.xml (should fix any mms issues, if it doesn't I'll change it to 5)
Kernel uploaded yesterday will still work (am using it right now)
Kernel Update (2012 April 18)
Uploaded a new kernel built from DooMLoRD's Sources (see links above) with wifi modules included (so you won't have to flash 'em) -- NOTE: THIS ONE WILL BREAK H/W DECODING.
Rom Update (2012 April 19)
Uploaded a new version.
1) Latest cm9 fixes
2) Tried adding some of the info from brainard52's post into the apns-conf.xml it it doesn't work, follow the instruction in his post (thanks brainard52!)
Rom Update (2012 April 21)
Uploaded a new version
1) Latest cm9 fixes
{in case mms is still not fixed 2) Tried adding some of the info from brainard52's post into the apns-conf.xml it it doesn't work, follow the instruction in his post (thanks brainard52!)
}
Why? Because 8 hours and still no upload from FXP, so I felt like uploading one
Rom Update (2012 April 25)
Uploaded a new version
1) Latest cm9 fixes
2) Included KeiranFTW's latest DFK-CM9 kernel in the zip, because well, it works. best. way to go keiran!
3) Made sure that ro.board is zeus, not zeusc (once again, thanks Keiran!)
Rom Update (2012 April 29)
1) Latest CM9 Fixes
2) zipalign in /system/xbin
3) OI File Manager From OpenIntents
4) Network Name fix from 216Monster!
Rom Update (2012 May 03)
1) Latest CM9 fixes
2) Change in baseband libs to .57.
Sorry, not too much this time, I got distracted with the 2.3.4 update & got to it late
Rom Update (2012 May 05)
Added Codename-Android to the download list. If you like tweaks, enjoy. Codename Android has it's own thread
Rom Update (2012 May 06)
1) Latest CM9 fixes... including theme manager! (but no themes, yet)
Rom Update (2012 May 09)
1) Latest CM9 fixes
Rom Update (2012 May 12)
1) Latest CM9 Fixes (sorry, nothing big this update, busy)
2) Also packaged latest DFK in zip
3) DO NOT USE FXP KERNEL WITH THIS ROM, I HAD MASSIVE FC ISSUES.
Rom Update (2012 June 6)
1) Been a little while hasn't it
2) Latest CM9 fixes
3) Kernel included was built from source as part of CM's new "inline kernel building" (FXP's kernel)
As Brainard52 Suggested,
Resources:
HOW TO FLASH A KERNEL:
1) Download a working kernel for CM9 (it's in download links, included with FXP zip & stand-alone (will be fixed next update))
2) extract kernel from where ever you downloaded it to where ever fastboot is (unless you add fastboot to $path in windows or /bin||/usr/bin||etc in linux)
3) type the following command "fastboot -i 0x0fce flash boot <name of boot.img>
4) NEVER FLASH RECOVERY.IMG.
Linux users:
If you create a file, 51.android.rules, put this in it
Code:
SUBSYSTEM=="usb", ATTR(idVendor)=="0fce", mode=="0666", GROUP="plugdev",
chmod it to 644 (r+w) & copy it to /etc/udev/rules.d/ you never need to use -i again! (for your play)
Links:
Flashtool:
http://forum.xda-developers.com/showthread.php?t=1351299
Original FXP Thread:
http://forum.xda-developers.com/showthread.php?t=1447542
Team Darkforest CM9 Kernel:
http://forum.xda-developers.com/showthread.php?t=1541482
Recovery:
http://forum.xda-developers.com/showthread.php?t=1130639
In case you want to try out building from source, read this link:
http://forum.xda-developers.com/showthread.php?t=1556971
Note: KeiranFTW forgets one major thing in his post, he assumes that somebody will only do it once! If you plan on doing it more than once, then for every git clone you do (msm-7x30, zeus, zeus-common in device/semc/ & vendor/semc/) you should go through and do a git pull everytime you wanna rebuild source (knowing Keiran, he probably just made a script for it )
If you want to build a kernel from source download this text file:
Kernel Tutorial! (Note: In it I use FXP sources, if you wanna Doom/Keiran just change the git url inside to their kernel sources)
Courtesy of CrimsonKnight13, Here is a list of apps that are a good addition to CM9
CrimsonKnight13 said:
Here's my list of preferred apps over stock CM9/ICS
ConnectBot > Terminal Emulator
Dolphin Browser HD (newest has an ICS-ish look) > Browser (Chrome)
exDialer w/ ICS Theme AC > Phone
Play Music > Music
SuperSU > Superuser
APEX Launcher > Trebuchet
Swiftkey 3 Beta (has a very ICS look) > Default keyboard
OpenExplorer Beta > File Explorer (from any ICS/CM9 iteration)
Alarm Clock Plus > Clock
Click to expand...
Click to collapse
I'm adding a poll on top to see what people want included. If an app is a paid app, then don't even think about asking for it to be added.
LOGCAT
For future reference, I'm going to include here how to use logcat (android debugging tool.)
There are two main ways to do a logcat, within android and through adb.
Logcat within android can be installed by a logcat app:
Two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging.
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
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)
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 search for an error in the logcat file (it's always e/ for error, f/ for fatal. those are the two main things that matter to me.)
Code:
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 <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService( 203): flags <[down]>
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 <manifest>: 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)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E -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!
How this relates to xLoud. (or any other problem we have with future updates.)
Now, since xLoud is apparently causing all sorts of havoc including not granting root , screwing up volume & messing with equalizers, a logcat done the following way will help me immensely with figuring out how to go about fixing it:
Code:
adb logcat *:E -v long > name of problem.txt
will print out all errors, fatal exceptions (what causes android to crash) that happen with the xLoud (or any other risky) update.
my email (for sending me logcats): [email protected]
Complaints, requests for add-ons, stupid questions, or anything else I feel like will be deleted upon receiving it. Logcats will not.
(If you wanna complain, request something or ask a stupid questions, that's why this thread is here)
Regarding Nightlies:
UPDATE:
Everybody: Head on over here -- http://forum.xda-developers.com/show....php?t=1661091
It's the nightly build for R800
Pax
Click to expand...
Click to collapse
UPDATE: Here is an update.zip file to automatically change any CM9 (AOSP ICS) based R800i download to work with the R800x (all thanks to KeiranFTW & Atarii for the fix)
saved for future use
Very nice.
Is the minmax governor in your kernel?
CrimsonKnight13 said:
Very nice.
Is the minmax governor in your kernel?
Click to expand...
Click to collapse
No, I have not messed with the kernel yet, after I get all the kinks out of my builds, I might start working with the kernel source.
Pax
paxChristos said:
No, I have not messed with the kernel yet, after I get all the kinks out of my builds, I might start working with the kernel source.
Pax
Click to expand...
Click to collapse
Your ROM & kernel will be my templates for my own. Finding time will be the issue...
Bluetooth Media Audio is also broken. Connects to phone audio fine, but media audio plays out of phone speakers.
EDIT: MMS does work as long as the verizon APN is set. I think Chevy includes it as part of his package, because I haven't had to manually set it since 112.
crono141 said:
Bluetooth Media Audio is also broken. Connects to phone audio fine, but media audio plays out of phone speakers.
Click to expand...
Click to collapse
Indeed, I confirmed this in the GSM CM9 Thread. I was watching my logcat as I connected my headphones up, you get a message from the AudioManager during the BT setup that it is changing things and routing audio to the speaker, which is clearly wrong.
It's coming from two separate processes though, so I gotta dust off my regex skillz to write a regex that'll pull in the messages from the BT process and the AudioManager process.
Whohoo! Welcome everyone! Anything cm9 cdma related put here instead of the fxp thread from now on since they won't pick us up for about another few months or so. Other then the obvious common sense things like being decent and patient with each other, it's time to bang our heads together and make our plays eat some ics!
Will be installing right now. Will let you know what I find (if anything)
ohh i know, get xloud working so i can actually hear my phone ring and notification sounds play and alarm go off. ^_^
DoomLoRD's ICS Beta DooMKerneL works with FXP, if you flash his wifi modules and run this command at boot: "insmod /system/lib/modules/bcm4329.ko"
Thanks to chevyowner for that command, I'd have never figured that out.
And if you want to have deep sleep, don't run that command to activate the wifi until you need it. I don't use wifi much, so I've got mine set up as a script in Rom Toolbox. When I need wifi, I run the script, then when I'm finished with wifi, I reboot.
{
"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"
}
A couple of things to mention here, since this is the ALL NEW FXP CDMA Thread !!!
You may recall I reported a problem with PACMAN for Xperia PLAY where it shows up in the market as incompatible, and it won't manually install from my backup of the apk. I have concluded this is definitely a compatibility issue with CM and possibly something needs added or edited in the build.prop to resolve it. I'm no dev, but I'll try to figure this out and get it working, which may also resolve some of the other so-called incompatible app issues.
Second item of note: The caps lock does not work in the standard keyboard. Normally you can click it twice to lock caps in, but not in CM9.
Third - well, there was a third, but now I've forgotten what it was, so I'll add it later!
10 char...
(xda emailed me your earlier post, I'll respond to that.)
FXP will always say FXP in the title, mine will have a date, both well be signed, just not in the title...
Sent from my R800x using Tapatalk
paxChristos said:
(xda emailed me your earlier post, I'll respond to that.)
FXP will always say FXP in the title, mine will have a date, both well be signed, just not in the title...
Sent from my R800x using Tapatalk
Click to expand...
Click to collapse
I swear I read your post about 10 times, I didn't read that part till the 11th
I am an idiot and I need help.I just unlocked tonight and afterwards I downloaded this,transfered to sd and attempted to install.It said the usual and hung at installing update.I did a battery pull(Im an idiot)and when I attempted to get into recovery I am froze at Sony screen.Suggestions?I am very new to the Play.
netizenmt said:
A couple of things to mention here, since this is the ALL NEW FXP CDMA Thread !!!
You may recall I reported a problem with PACMAN for Xperia PLAY where it shows up in the market as incompatible, and it won't manually install from my backup of the apk. I have concluded this is definitely a compatibility issue with CM and possibly something needs added or edited in the build.prop to resolve it. I'm no dev, but I'll try to figure this out and get it working, which may also resolve some of the other so-called incompatible app issues.
Second item of note: The caps lock does not work in the standard keyboard. Normally you can click it twice to lock caps in, but not in CM9.
Third - well, there was a third, but now I've forgotten what it was, so I'll add it later!
Click to expand...
Click to collapse
The real question is has ANYONE been able to install/launch Pacman in ICS on the Play? Perhaps it is a compatibility issue with the game itself that needs an update from Namco in order to support ICS? I think that is more likely...
Taken that in reverse, GTA III will not install in GB, but allows me to install fine in ICS
bob24260 said:
I am an idiot and I need help.I just unlocked tonight and afterwards I downloaded this,transfered to sd and attempted to install.It said the usual and hung at installing update.I did a battery pull(Im an idiot)and when I attempted to get into recovery I am froze at Sony screen.Suggestions?I am very new to the Play.
Click to expand...
Click to collapse
did you flash a kernel? (fastboot -i 0x0fce flash boot boot.img)
Spam the back button upon boot (it might be the volume rocker, I'm not 100% sure)
That should get you into recovery.
Sent from my R800x using Tapatalk
I tried like crazyto get into recovery via volume down which is how i got in before unlocking.I am very new to play and I am absolutely bummed that i have a new brick
---------- Post added at 01:31 AM ---------- Previous post was at 01:30 AM ----------
I was installing via sd just as the post said and when it hung I did a battery pull
---------- Post added at 01:32 AM ---------- Previous post was at 01:31 AM ----------
I have fastboot up.Is there a command you could show me how to run that would help?
---------- Post added at 01:34 AM ---------- Previous post was at 01:32 AM ----------
I appreciate any help given.I feel like such an idiot

[ROM][WIP] CM10.2 Badadroid v3.1

CM10.2 for WAVE and WAVE 2
Android Jellybean 4.3.1​
Hi All,
So once again it’s time to upgrade our project to Android 4.3.1
Previous versions:
CM10: forum.xda-developers.com/showthread.php?t=1851818
CM10.1: http://forum.xda-developers.com/showthread.php?t=2400126
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FEATURES
Android 4.3.1
CM sources of 21.10.2013
Updated to linux kernel version 3.0.101
270 MB RAM
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- GPS - http://forum.xda-developers.com/showpost.php?p=47209249&postcount=1371
- Conference Calls
- Some problems with audio codec settings, but generally it should
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-10.2 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.1/local_manifest.xm
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
cd .repo
wget [url]https://raw.github.com/Badadroid/android_wave_local_manifest/cm-10.2/local_manifest.xml[/url]
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM from CHANGELOG section
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition or SD Card.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- "install zip"
- "choose zip from from storage/sdcard1"(Bada's User partition) or "choose zip from storage/sdcard0"(SD Card)
- cm-10.2-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
After first installation i recommend to disable Screen-off Animation by Settings->Display-> uncheck Scren-off animation
And also for better performance activate zRAM. Settings->Performance->Memory Management->zRam-> and choice Value. I use 26%
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS http://d-h.st/mBO from http://forum.xda-developers.com/showthread.php?p=47934744
Minimized by -CALIBAN666- from PA GAPPS: http://forum.xda-developers.com/sho...ers.com/showpost.php?p=35107469&postcount=393
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
CHANGELOG:
Kernel update
http://www.multiupload.nl/TWJAP1T4C9
kernel with removed +10 RAM patch for v3.1 with working camera and video playback
v3.1 - http://www.multiupload.nl/1E85FRD1ES
- +10mb RAM
- Updated audio codec settings for RCV and HP
- Added 15 volume levels for Calls
- Reworked SMS sending
- Fixed torch toggle in quick settings.
Kernel update for Wave2
for fixinginstallation problems
http://www.multiupload.nl/O2CVN5R9EQ
Replace zImage in Zip with this and re-copy it on Bada User Partition
and after flash step by step.
If you forgot or don't want to pack zImage in zip archive you need again replace zImage on Bada User's partition, because during flashing zImage will be replaced by one from zip archive.
Big Thanks to Rebellos for logs and RedDerRed from badapps.ru for testing all my test versions
v3 Initial CM10.2 release: http://www.multiupload.nl/8UUFOIQQE1
- Updated kernel 3.0.101
- CM Sources 30.11.2013
- CM team fixed power menu on lock key. Now we can show power menu by long press of lock key.
So i don't see any reason to use Navbar. We back to Galaxy S mapping:
Call key = MENU
Middle key = HOME
End Call key = BACK
Lock key = POWER
- Removed VideoEditer, LiveWallpapers, CMUpdater
- Fixed BT headset in calls
- Set of patches for GPRS RIL interface
- Fixed memory leaks in SIM_IO requests
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
Nice Work Volk & Rebellos
Work this Version faster ?
Greets
Sent from my GT-N7100 using xda app-developers app
Nice work
very fast and smooth........awesome work :good::good::good:
incredible speed without gapps
anyway of installing just google calendar and google contact sync? (without the whole gapps package)
thank u so much @volk204.
but this rom still not smooth and its slow , and there is no Bigmem , bigmem 325mb ram will make this rom competely usable and really realy faster and great for gaming
i m 101% sure latest games like asphalt8:airborne , Modern combat 4,5 will not work.
even normal apps will lag too
wave 2 does not work ...
Gunter33 said:
wave 2 does not work ...
Click to expand...
Click to collapse
same too.
gonghwa said:
same too.
Click to expand...
Click to collapse
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
jon.marius87 said:
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
Click to expand...
Click to collapse
same too(((
4.3
volk204 said:
CM10.1 for WAVE and WAVE 2
Android Jellybean 4.3.1​
Click to expand...
Click to collapse
Sorry to point out but Android 4.3 is CM 10.2...
Gunter33 said:
wave 2 does not work ...
Click to expand...
Click to collapse
djkoloda said:
same too(((
Click to expand...
Click to collapse
Very verbose bug report.
jon.marius87 said:
for me can get into recovery mode but when it's Chose zip from/storage/sdcard0 shows me E: Can mount/storage/sdcard0. hmmm something is strange: (
Click to expand...
Click to collapse
gonghwa said:
same too.
Click to expand...
Click to collapse
Do you have SD CARD? Can you mount storage/sdcard1(Bada user's partition)?
Sandeep Srikantam said:
Sorry to point out but Android 4.3 is CM 10.2...
Click to expand...
Click to collapse
Fixed
Very good job :good:
at the choice of Chose zip from/storage/sdcard0 shows me E : Can mount/storage/sdcard0. at a copy on sd-card the same result. wave s8530
lack of torch in quick settings
Hello. I've noticed there's no torch in quick settings. I think it maye be fixed by adding:
Code:
<bool name="has_led_flash">true</bool>
in:
Code:
https://github.com/Badadroid/android_device_samsung_wave/blob/cm-10.2/overlay/packages/apps/Settings/res/values/config.xml
but i'm not sure (cm-10.1 had this line and torch was in there, as u can see)
Code:
https://github.com/Badadroid/android_device_samsung_wave/blob/cm-10.1/overlay/packages/apps/Settings/res/values/config.xml
i can't find anything that could change it in rom .zip package so i think it will be just information for future roms.
very good sir
Good job
Good job bro continue like that !
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
waveguru said:
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
Click to expand...
Click to collapse
Maybe memory corruption, happened to me also, try to reflash bada then reinstall android
waveguru said:
Hi volk204,
I am unable to install new ROM on wave 2.
In CWM mode,its showing message..
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
when i click on "install zip"..
it showing "choose zip from /storage/sdcard0"
also,I am able to mount /bada-user.
Thanks,
Waveguru
Click to expand...
Click to collapse
I have a same problem with you. it's not working on Wave II
I installed Bada again and tryed once more but same. I'm choosing -choose zip from/storage/sdcard0 but nohing happening. I also formated sd card again and tryed to put 10.2 v3 zip to phone memory but same...
volk204 said:
Very verbose bug report.
Do you have SD CARD? Can you mount storage/sdcard1(Bada user's partition)?
Fixed
Click to expand...
Click to collapse
I referred to this Q&A
Badadroid is stuck in animation with rotating circle where Cyanogenmod is written in
It happens if you don't comply with installation requirements. Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
150MB of free "User" memory
400MB of free "Applications" memory
Solution: make a clean installation of bada: full flash
Related XDA posts: http://forum.xda-developers.com/showthread.php?p=39859136#post39859136
and after I checked the phone the answer is yes, I have less memory than required. After a full flash I got no luck to get v3 running. I guess it is related with the kernel because if I change kernel to v2.1's it can flash the v3 zip and later show some progress during the rolling circle. If I use kernel in v3 zip it just can't mount sdcard0 as others. That's all I can provide.

[ROM][WIP] CM11 Badadroid v4.4

CM11 for WAVE and WAVE 2
Android Kitkat 4.4.2​
Hi All,
So once again it’s time to upgrade our project to Android 4.4.2
Previous versions:
CM10: http://forum.xda-developers.com/showthread.php?t=1851818
CM10.1: http://forum.xda-developers.com/showthread.php?t=2400126
CM10.2: http://forum.xda-developers.com/showthread.php?t=2550138
Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
FEATURES
Android 4.4.2
CM sources of 13.01.2014
Updated to linux kernel version 3.0.101
270 MB RAM
KNOWN BUGS (what doesn't work):
- Network registration don't work with some SIM cards
- Conference Calls
- Some problems with audio codec settings, but generally it should
- Impossible to shut down phone in android, only restart
- Don't leave phone charging without supervising - if it gets enormously hot, disconnect it - this can literally blow up battery as there is no overheating protection yet. Do not leave it connected on 100% - it'll discharge by 1% all the time, and then recharge, what's very unhealthy for battery.
Maybe something else, what i forgot
SUPPORT
You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it, use Bada or other releases.
We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the Android, and/or other things that might be relevant.
Please join us on IRC: some people are on #badadroid (freenode).
BUG REPORTS
This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad.
You’ll have to wait then.
If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.
Please attach logcat and dmesg dump in your bug report. Dmesg should contain messages from both - bootup and issue occuring (you can't dump it 1 hour after bootup, rather 2 minutes after)
How to dump logs - Google for "android logcat dmesg" Or... whatever, here's one of 3204109 methods available.
In the Terminal Emulator enter:
"su"
Accept request for SuperUser access.
"dmesg > /storage/sdcard1/dmesg.txt"
"logcat -b system -b radio -b events -b main -d -f /storage/sdcard1/logcat.txt *:V"
"logcat -b radio -d -f /storage/sdcard1/radiolog.txt *:V"
Download them from phone, archive and upload them.
Privacy warning: Your logcat might contain sensitive information like your IMEI, IMSI, cell stations you were nearby, numbers you called and got calls from and SMS sent and received. If you don't want to publish this info - send them privately to one of developers.
Click to expand...
Click to collapse
If the Badadroid is restarting before you're able to catch any log:
Download http://goo.im/devs/Rebellos/wave/bterm.exe
Try to start kernel normally, when you see Badadroid logo start holding the middle key pressed. Keep the middle key pressed until phone restarts and shows the text: FOTA DOWNLOAD MODE & bTerm
Connect phone to PC.
Start bterm.exe
Type 4 commands:
Code:
open
dumpram 0x4FF00000 0x100000
close
exit
There should appear file called dump_ram_0x4FF00000.0x00100000.bin - pack it and attach it to your bug report.
Click to expand...
Click to collapse
Bug reports without logs are completely useless.
NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.
I do heavily encourage to work together on the better, common project instead of making kang releases and demanding money for somebody else's work.
Read as: If you think you can make something better than this by doing less and muchazo Ctrl+C Ctrl+V - you suck, go figure the rest.
HOW TO BUILD
I do recommend perfect tutorial by fattire: https://docs.google.com/document/d/19f7Z1rxJHa5grNlNFSkh7hQ0LmDOuPdKMQUg8HFiyzs/edit?hl=en_US
Of course you have to init with -b cm-11.0 and modify some steps.
local manifest to use: https://raw.github.com/Badadroid/android_wave_local_manifest/cm-11.0/local_manifest.xml
I do it like this:
Code:
cd ~
mkdir wave
cd wave
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
cd .repo
wget https://raw.github.com/Badadroid/android_wave_local_manifest/cm-11.0/local_manifest.xml
cd ..
repo sync -j8
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
brunch wave
device name is wave so the build invocation can be brunch wave
FIRST INSTALLATION
Bada 2.0 is required
Enter Bada Settings->General->Memory and make sure you have at least:
370MB of free "System" memory
160MB of free "User" memory
400MB of free "Applications" memory
Download BOOTFILES, armlinux_boot for your device:
for 8500:
http://yadi.sk/d/W4RjnjQRC6TfP
http://yadi.sk/d/Yz7_dfpkC6TkC
for 8530
http://yadi.sk/d/kxJ0CZ20C7AKF
http://yadi.sk/d/zqzWZ9LmC7AJA
(please pay attention if it's S8500 or S8530 BOOTFILES and FOTA you're choosing!):
Download ROM from CHANGELOG section
Start Bada.
Extract zImage from zip and copy it to the Bada's User partition (the one about 390MB big).
Copy whole .zip to the Bada's User partition or SD Card.
Flash BOOTFILES and FOTA using Multiloader.
Reboot the phone holding Power and Call key.
FOTA set of red messages should appear, after about 15seconds Badadroid logo shows up.
Be patient, first bootup will keep unresponsible on Badadroid logo for up to 5 minutes.
CWM Recovery starts, pick:
- "install zip"
- "choose zip from from storage/sdcard1"(Bada's User partition) or "choose zip from storage/sdcard0"(SD Card)
- cm-11-wave-<release id>.zip
- Yes - install
Reboot holding the Power key
You can remove installation .zip from the User partition from Android level by connecting through USB in MTP mode.
Do not remove zImage file.
Normal bootup is available using Power+Call keys
CWM Recovery mode is available using Power+Volume Up keys
CWM Flashing does overwrite zImage. So every next update you can just flash .zip through CWM.
For activation Performance and Developer Options categories in Settings you need Settings->About Phone and tap 7 times on Build number
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
SLIM GAPPS: http://d-h.st/users/ZordanKV/?fld_id=28623#files
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/showpost.php?p=35107469&postcount=393
THANKS TO
Special thanks to Rebellos for his CM10 ROM, for his good sources and many time, what he spent for my learning
Another Badadroid devs: Oleg_k, mijoma, nbates66, anghelyi, mikegapinski, hunktb, autra, Tigrouzen and many others.
CyanogenMod team for base ROM
Pawitp, kasper_h and all other aries developers
Paulk and Replicant project for good base for bada-modem RIL
and many other who help us.
CHANGELOG:
v4.4 http://www.multiupload.nl/SX2RTH51BC
- CM sources 2.06.2014
- Patches from SGS
v4.3 http://www.multiupload.nl/QS4A17BXXW
- CM sources 30.03.2014
- Many changes from CM core team
- Kernel with new optimization (Last Mackay Kernel from Nameless ROM)(new Zram algorithm, GPU fixes and etc. )
- Included fix for Wave2 from chemosun. This patch reduce Wave 2 screen wake up bug, i don't know about battery drain. He sent me it several months ago, but i forgot to include it to previous release
- Screen Frame rate path. Thanks to Alberto96
- Disabled 720p recording/playback. Big thanks to Alberto96 for idea and sources. It gave us more RAM.(total available in ROM 283MB) It is correctly disabled in ROM. so Photo camera is fully working, video camera is only 480p. For 720p playback you can use third-party apps like MXPlayer and etc.
If you go from previous releases, you need to clean data for Gallery and Camera application
v4.2 http://www.multiupload.nl/ZGB2Z5YOWD
- CM sources 21.02.2014
- Many changes from CM core team
-Added Basic GPS
v4.1.1 http://www.multiupload.nl/B7M535UJXH
- CM Sources 01.02.2014
- Zram 120Mb by default
- Some improvements for bootanimation
- Fixed some mistake in init, which can be the reason of some wi-fi problems
v4.1 http://www.multiupload.nl/5L9CCWZ4XA
- CM sources 28.01.2014
- Many changes from CM core team: Call delay workaround by pawitp was merged to CM sources, so no need to flash it
- Added test Battery thread to RIL https://github.com/Badadroid/androi...mmit/65d8d549e52761a9b8b673a0620c108773cf9ffd
- Added overlay for hardware camera key
v4 Initial CM11 release: http://www.multiupload.nl/YHC2P74SJZ
- CM Sources 13.01.2014
- Big patch set from mackay kernel http://forum.xda-developers.com/showthread.php?t=2532813 :
updated CPU governors, I/O schedulers, and many other performance patches
- 80Mb zRAM
MORE LINKS
Overall project thread - http://forum.xda-developers.com/showthread.php?t=1459391
question
thanks for update
this cm11 is running dalvik or art?
black0000 said:
thanks for update
this cm11 is running dalvik or art?
Click to expand...
Click to collapse
Dalvik is default Android Runtime for all kitkat ROMs.
Art is experimental feature from Google and still is WIP:
You can read more here:
http://source.android.com/devices/tech/dalvik/art.html
CM officially don't support Art, though it is possible to switch to Art in developer options
volk204 said:
Dalvik is default Android Runtime for all kitkat ROMs.
Art is experimental feature from Google and still is WIP:
You can read more here:
http://source.android.com/devices/tech/dalvik/art.html
CM officially don't support Art, though it is possible to switch to Art in developer options
Click to expand...
Click to collapse
according to you which one is better dalvik or art gor our wave
black0000 said:
according to you which one is better dalvik or art gor our wave
Click to expand...
Click to collapse
I didn't try Art, i can say that after last optimization changes performance is good enough even with dalvik.
@hero355, what you can say about performance of this ROM after playing Asphalt 7 on it?
volk204 said:
I didn't try Art, i can say that after last optimization changes performance is good enough even with dalvik.
@hero355, what you can say about performance of this ROM after playing Asphalt 7 on it?
Click to expand...
Click to collapse
Firstly I want to say big that's to volk204 for his great work
This time really it's a big step in badadroid development.
I've tested several kernel and I can say The phone is simply flying,The performance and optimization is perfect and we got now almost stable for 4 years old Samsung Wave phones
Secondly I've tested game performance and my tests was on Asphalt 7, (I haven't time for test other games- I'm not a gamer )
As you know there are some kernels with bigmem and zram .
I've tested all kernels with asphalt 7 and while all my tests I used 100~1000 MHz with interactive governor and game was running perfect
The best game performance was zram 120 with 1000mhz, I don't even imagine that with bigmem zram120 + 1400mhz it'll fly
So I can say now time to revert android to default
Thanks again volk204 and all badadroid developers
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Stevethegreat said:
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Click to expand...
Click to collapse
AFAIK camera is not working at all and photo also on Bigmem, added to OP, but i really don't see anysense to use bigmem, because in normal mode all is OK))
volk204 said:
AFAIK camera is not working at all and photo also on Bigmem, added to OP, but i really don't see anysense to use bigmem, because in normal mode all is OK))
Click to expand...
Click to collapse
Hey, nice work as always! But any chance of NAND version for this ROM?
Or can we use without bada n Tigrouzens Fota?
Stevethegreat said:
Question: does the bigmem kernel allow photo taking? I can live without video but not without camera/flashlight...
Click to expand...
Click to collapse
No, camera app will not work, so no photos and video capturing.
sadiq23 said:
Hey, nice work as always! But any chance of NAND version for this ROM?
Or can we use without bada n Tigrouzens Fota?
Click to expand...
Click to collapse
No correct charger - No NAND version
volk204 said:
HOW TO UNINSTALL
Follow the steps there: http://forum.xda-developers.com/show...&postcount=393
Click to expand...
Click to collapse
The Link is not functional anymore. Shows that the forum specified is invalid.
Sandeep Srikantam said:
The Link is not functional anymore. Shows that the forum specified is invalid.
Click to expand...
Click to collapse
fixed
GAPPs
volk204 said:
fixed
Click to expand...
Click to collapse
There are two files in Slim GAPPs, test(newer) and an older version. Which one to download ?
Is this version noticeably faster than the previous one (3.1)?
WiFi Not Working
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
WaveII_Jil said:
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
Click to expand...
Click to collapse
Search for Wifi fix zip , I don't know where is ,I think in 3.1 or 2.1 thread
WaveII_Jil said:
@volk204, I was running CM Badadroid v2.1 and today I installed CM11 Badadroid v4. Since then the Wifi is not working on my wave 2 s8530.
Other devices are detecting the Wifi and connecting to it but my wave is not connecting to the wifi.
I have also disconnected other devices and tried to connect only wave 2 but the device doesn't even detect wifi network.
Please help.
Click to expand...
Click to collapse
anyone with wave2 has the same problem?
Did you do clean installation with removing previous version of android and installing new version or just flashed zip via recovery?
No logs - no problems
florynwk3 said:
Search for Wifi fix zip , I don't know where is ,I think in 3.1 or 2.1 thread
Click to expand...
Click to collapse
It is useless
volk204 said:
anyone with wave2 has the same problem?
Did you do clean installation with removing previous version of android and installing new version or just flashed zip via recovery?
No logs - no problems
Click to expand...
Click to collapse
I did a clean installation by uninstalling previous version and installing new version. Sorry, could not get the logs.
Just wanted to know if this issue exists only in my phone or others also...
BUG: encrypt device ...
hi folks,
great work volk thats really exciting..
the interesting lines are:
ActivityManager( 503): Resuming delayed broadcast
I/ActivityManager( 1035): Timeline: Activity_launch_request id:com.android.settings time:3037005
I/ActivityManager( 503): START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from pid 1035
D/PhoneStatusBar( 658): disable: < EXPAND* ICONS* ALERTS* ticker SYSTEM_INFO* BACK* HOME* RECENT* clock SEARCH* >
I/ActivityManager( 503): Displayed com.android.settings/.CryptKeeperConfirm$Blank: +359ms
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3037409
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41d115a0 u0 com.android.settings/.CryptKeeperConfirm$Blank t4} time:3037702
E/Cryptfs ( 156): Cannot get size of block device
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3047091
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41ca10d0 u0 com.android.settings/.SubSettings t4} time:3047384
D/Tethering( 503): Exception adding default nw to upstreamIfaceTypes: java.lang.NullPointerException
I/ActivityManager( 1035): Timeline: Activity_launch_request id:com.android.settings time:3051736
I/ActivityManager( 503): START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from pid 1035
I/ActivityManager( 503): Displayed com.android.settings/.CryptKeeperConfirm$Blank: +103ms
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3051879
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41cbcb58 u0 com.android.settings/.CryptKeeperConfirm$Blank t4} time:3052206
E/Cryptfs ( 156): Cannot get size of block device
I/ActivityManager( 1035): Timeline: Activity_idle id: [email protected] time:3060969
I/ActivityManager( 503): Timeline: Activity_windows_visible id: ActivityRecord{41ca10d0 u0 com.android.settings/.SubSettings t4} time:3061295
I think
E/Cryptfs ( 156): Cannot get size of block device
is the line to be interpreted...
Can someone please have a look into it...
logcat & co are attached

[Developer Only] - L Port [Broken/WIP]

OKay So I thought I would try to port the latest beta of L to our OnePlus One. Never really ported before and mainly followed this thread here: http://forum.xda-developers.com/showthread.php?t=1908008
Currently I have it installing and booting to the boot animation and playing the boot animation (whooo) but thats as far as it goes. Unfortunately usb isn't recognized when I plug it in. Is there any way I can get some sort of log?
Its based on the latest nexus 5 L rom.
here is the zip file. Its broken, under no circumstance should you install this unless you are a developer.
Code:
DO NOT INSTALL IF YOU AREN'T A DEVELOPER
AOSP BASE
PA BASE
Current logcat on boot for PA:
http://pastebin.com/c5J0cmQ8
Can't get logcat on boot for AOSP base
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Nice of you that you even tried it! Maybe you developers should port this together in teamwork? Everybody has problems with L on the OPO, maybe together you can solve them
Did you tried it with OnePlus AOSP?
You guys might benefit from the discussion here:
http://forum.xda-developers.com/showthread.php?t=2829974
Transmitted via Bacon
---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
phoenixita said:
Instead of AOSPA try using the official Oneplus AOSP rom as base. Let me know.
Click to expand...
Click to collapse
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
aeppacher said:
just tried with aosp and although file structures and update scripts seemed more similar, I can't get a logcat and I am still stuck at a bootanimation
Click to expand...
Click to collapse
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
eugenioxx said:
There are some error with camera and sound :
E/AudioDaemon( 245): Open /proc/asound/card---/state failed : No such file or directory
[...]
E/mm-camera( 243): vpe_module_create_vpe_ctrl:141, failed, cannnot create vpe hardware instance
E/mm-camera( 243): vpe_module_init:34 failed
E/mm-camera( 243): c2d_module_init:28 name=c2d
E/mm-camera( 243): c2d_module_init:67: info: C2D module_init successful
E/mm-camera-img( 243): cac_comp_load:656] Error opening CAC library
E/mm-camera( 243): module_cac_init:1028] Error rc -6
E/mm-camera( 243): pproc_module_init:2175] cac module create failed
I don't know exactly why...
Maybe tomorrow and next week I'll try too
@aeppacher are you using latest android 5.0 preview LPX13D?
Click to expand...
Click to collapse
yes I am. I am posting my attempt at the aosp port with the LPX13D as well. Adb isn't grabbing a logcat for me unfortunately
Hopefully devs can help this would be sweet
Hit Thanks if I Helped
-_-NAMELESS ROM 1+1-_-
Hey man i'm no dev, but I just shared your post on Reddit (r/Android and r/oneplus) hopefully more devs will see this and come assist you I would love a port!
Just like previously mentioned I think you guys would benefit from the discussion in the thread previously posted. Better yet pm the developer who recently tried so you at least rule out some things that may have been previously attempted. Good luck guys
You cant port different version of Android by drag-and-droping system folders.
It'll probably be easier once retail Lollipop is out and open sourced on AOSP project. But TBH Cyanogenmod historically has put out builds really fast for nexus devices and ours is nexus-ish. I'll try my luck with kanging CM once they put something out for the N5 or N6.
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
Ha, no.
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
This
Sent from my X9006 using XDA Free mobile app
CraZY_BoY^ said:
You cant port different version of Android by drag-and-droping system folders.
Click to expand...
Click to collapse
suraj.das said:
This
Click to expand...
Click to collapse
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Alzoids said:
Yes, this is not what they're doing. That would be idiotic. They're trying to port it.
Click to expand...
Click to collapse
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
Should have included a "/s" I guess.
Sorry man, but when you are making this big of a switch. Especially different device AND different version of android, there is more that the drag and drop tutorial to this. You actually need to know the languages its developed is so you can find what's wrong with it and in turn, you can create your own fix. (Simple terms here)
Basically, you need to be able to write a compliant device tree and kernel that can compile with the new source.
TiVON said:
Check the link the OP has used to port. It's exactly what he's doing!
You need more skills than that to accomplish this!
Click to expand...
Click to collapse
sorry to go off topic but your DP suits the situation lol

MTCB/MTCC rk3188 (5.1.1) Firmware with an xposed set of MTC apps

Based on latest LOLLIPOP with MICRO GAPS and OPEN GAPS 1024 x 600 and 800 x 480 from @dsa8310.
Sharing with you my custom modified rom with LP image.
UPDATE 29.8.2017:
MicroG version: 1024 x 600 and 800 x 480
- added screen saver with speed, clock and apps shortcut ported from well known developer @Malaysk (null null still present)
(if someone need: screen saver in the attachement - replace with root explorer: system - app - mtcscreenclock
MTCScreenClock (round)
- 1024 x 600 resolutions has different radio and bluetooth apk
- included all xposed modules and fast google maps
- remember to enable all xposed modules and copy folder contents to external gps card!!!
Enjoy
UPDATE: 3.9.2017 LINKS UP 2019
microGaps version:
Lite 1024x600 microG version.
openGaps version:
Lite 1024 x 600 openG version.
Lite 800 x 480 openG version.
___________________________________________________________________________________
- LITE version of system
- added xposed status bar module for remove status bar items (copy mtc-status bar to external GPS Card)
- new screen saver without null null text (if doesn't show install it manually from: system/app/mtcscreensaver)
- removed all the bloatware callendar, calculator etc...
- added a lot of tweaks to speed the units with 1gb ram
- added new car launcher AG (trial) for me the best - full version 1€
- new xposed mtc manager 2.5 module
LITE VERSION OPTIMIZATIONS:
- kernel tweaks (changed parameters of dalvik vm etc,...)
- better ram management
- faster scrolling
- faster boot
- better responsiveness
- increased performance and app ram management
- better video acceleration
- disable sending android logging stuff
- force gpu&cpu rendering
System now uses less than 470 Mb of ram
BEFORE YOU START:
1. With disable service app find google play store and disable the first 5 services from top including DailyHygiene.
2. Login to MicroG
3. In microG settings enable google device registration
4. Clear data on Google playstore or clear from recents
5. Enjoy fast 5.1.11. playstore (if not showing paid apps just restart HU)
MTCB MCU USERS
- DSA's mtcxp xposed module has to be enabled before the status bar will show.
PREINSTALLED APPS and MODULES:
All these apps and xposed modules are preinstalled and you just have to activate xposed modules you need:
- disable_service
- google-maps-9.2 (you can update it just install as normal apk)
- mtcservice-2.60
- mtcsound-2.0.5 (remove from xposed if you don't have sound mod for better performance)
- mtcxp-1.0
- quickreboot
- RootExplorer
- Titanium_Backup
- xposed-disablefullscreenkeyboard
- xposed-mtc-bt-2.3
- xposed-mtc-keys-5.2 (custom keys for harware buttons)
- xposed-mtc-manager-2.5 (mode button mod and no closing apps when starting the car, etc.)
- xposed-mtc-music-2.8
- xposed-mtc-poweramp-1.4 (working media keys and stopping power amp when mtc app is started)
- xposed-mtc-radio-1.11
- xposed-VolumeBar (replaces original volume bar)
- 7th floor sound mod preinstalled and working
OTHER ADDITIONS: (included in download to copy on external SD (GPS card)
There is also file to copy on SD card (GPS card) that has features for MTCManager:
- hardware mode button can be configured (included in download) as well to switch between apps and auto play them (radio, poweramp, music, pcradio etc)
- mtc screen clock
- mtc status bar
DISABLING THE SCREEN SAVER OR CHANGING TIME:
Edit on external SD/ GPS-Card : Mtc.Manager/settings.ini
# the inclusion of an alternative screen saver, when you specify false will work full-time mechanism:
screenClock=false or true to activate
# Time off the screen if you do not set out full-time settings will be used in sec:
screenTimeout=300
# The name of the screensaver program package
screenPackage=com.microntek.screenclock
# Name Activiti screensaver
screenClass=MainActivity
# If the name of the package and Activiti is not specified, it will use a standard screensaver
MTC MANAGER CAPABILITIES:
capabilities
All configuration files must be on the external map in the mtc-manager directory.
1. The module carries the functionality of xposed-mcu , which does not allow the radio to go to sleep during the scrolling of the starter.
- when receiving a signal to turn off the module delays for 5 seconds, if at that moment the power reappears, nothing happens, in the absence of power, the radio recovers into sleep.
Due to the features of the implementation of the inclusion in our MCU, the screen goes out for the time of voltage failure.
This functionality can be disabled in settings.ini:
Settings.ini
Mcu_power = false
2. The module has a white list of applications that does not allow the system to close necessary services and applications when going to sleep and when pressing the "Acceleration" button in the blind. Thus, the module allows to refuse from using mtc-wakeup-service .
Filename with exceptions whitelist.ini
The file name of the white list application packages must be listed.
#
example
3. Accelerated start of user services. The services are started when the system kernel is loaded.
The list of services should be on the external map in the mtc-manager directory, the file name start_services.ini
each line should contain the service name in the format package name / full service name,
#
example
4. An alternative screensaver with a list of exceptions, running in any (even a non-standard application). The standard screen saver mechanism is activated.
It may not work on all firmware.
Settings in the settings.ini file.
Settings.ini
# Inclusion of an alternative screensaver, if false, the standard mechanism will work:
screenClock = true
# screen off time, if not specified, the value from the
default settings will be used: screenTimeout = 60
# screen saver program name
screenPackage = com.microntek.screenclock
# screen saver activation name
ScreenClass = MainActivity
# if the package name and activations are not specified, then the standard screensaver will be used
The exception list is located in the ss_exceptions.ini file - the package names must be listed, for example:
Ss_exceptions.ini
com.microntek.music
ru.yandex.yandexmaps
Also the screensaver will not start when talking on the phone, the rear view camera, navigation and turning off the radio.
If instead of a beautiful clock MTCSreenClock.apk a screensaver with a standard digital clock on a black background is called, you need to make sure that the MTCScreenClock application is installed.
If the application is installed, you can try setting screenPackage and screenClass parameters in settings.ini
5. Also in the module there is a "backup" for correct sound adjustment in MTC-Volume and MTC-Service .
#
The adjustment of sound in firmware on Android 4.4.4
6. Re-designation of OBD-device bluetooth.
Device names must be listed in the settings.ini file in obd_device parameter, separated by commas, in the form in which they are visible in the standard hands-free application. You can specify not names, but parts of names, for example:
Settings.ini
Obd_device = OBD, DUAL-SPP
7. Set the list of programs that are switched by the MODE button,
In settings.ini, set
Settings.ini
ModeSwitch = true
Programs are switched sequentially one after the other.
For correct sound switching, the applications used must be managed (play / pause) programmatically via intents. If the player does not support the start and stop playback of external intents, then you have to manually switch the sound.
When you click on the MODE button, the active application is searched for in the running list. Next, the application is sent a command (configurable in mode.ini) to close or pause the audio stream. After that, the default activation for the next application is launched and the application is sent a command to start playback (also configured in mode.ini)
#
Mode.ini
8. Disable the launch of the last running program.
Settings.ini
Clear_last_app = true
9. GPS time synchronization.
Settings.ini
Sync_gps_time = true
10. Turn on w-fi at startup.
Settings.ini
Wifi.on = true
Paypal:
https://paypal.me/johnydj?locale.x=en_US
Hello,
Please help me a little, it was a more than one year since I updated my fw.
How do I update to this firmware, I forgot the procedure?
Is it clean install, all apps/data are going to be wiped and must be installed again?
Is there a way to backup current firmware/apps, like twrp image or something (in case something goes wrong)?
Thank you
grgart said:
Hello,
Please help me a little, it was a more than one year since I updated my fw.
How do I update to this firmware, I forgot the procedure?
Is it clean install, all apps/data are going to be wiped and must be installed again?
Is there a way to backup current firmware/apps, like twrp image or something (in case something goes wrong)?
Thank you
Click to expand...
Click to collapse
Backup with titanium backup all your apps you want.
wipe data/factory reset from recovery, then flash the image with clear all
With titanium backup restore your apps back, thats it.
hi johnny,
would like to check if u manage to solve these issues of
1. xposed volume bar in the center of screen instead of bottom
2. misaligned apps buttons in mtcbluetooth mtcwheelstudy etc.
thank you in advance
jun81 said:
hi johnny,
would like to check if u manage to solve these issues of
1. xposed volume bar in the center of screen instead of bottom
2. misaligned apps buttons in mtcbluetooth mtcwheelstudy etc.
thank you in advance
Click to expand...
Click to collapse
1. Did you activate xposed mtc manager module in xposed app ?
2. Can you post picture, I didn't experienced this issue on my unit using the same image...
3. Please note this is 1024 x 600 resolution image...flashing on 800 x 480 can couse this issues you have...
Will post pic once I get a chance. Had no problem with gui using the dsa's last dec 5.1.1 rom.
jun81 said:
Will post pic once I get a chance. Had no problem with gui using the dsa's last dec 5.1.1 rom.
Click to expand...
Click to collapse
I added screen saver in latest version. But still don't know why you have problems with resolution. I can upload stock apps and you can try if there is also problem or not...
What are the performance benefits from the dsa8310 rom on a 1gb ram headunit?
I'm currently running dsa8310 latest 5.1.1. on my 1gb headunit. What sort of advantages will I see if I flash to your rom?
iselfdevi said:
What are the performance benefits from the dsa8310 rom on a 1gb ram headunit?
I'm currently running dsa8310 latest 5.1.1. on my 1gb headunit. What sort of advantages will I see if I flash to your rom?
Click to expand...
Click to collapse
Hard to say without knowing the exact version of his ROM youre running currently, but generally its a good idea to update the software as it is on any computer/smartphone/tablet. You shouldnt have to wipe data if youre already using it.
Read the thread to see the improvements that have been made recently - he lists them all.
Waiting for the 800 x 480 version !
champikasam said:
Waiting for the 800 x 480 version !
Click to expand...
Click to collapse
Done, check it out
Johny DJ said:
Done, check it out
Click to expand...
Click to collapse
Awesome ! Will check and let you know
---------- Post added at 04:39 PM ---------- Previous post was at 04:06 PM ----------
Johny DJ said:
Done, check it out
Click to expand...
Click to collapse
Could you check whether 800 x 480 img file is properly formatted ? I'm unable to mount or extract it. Getting an error saying the img file is corrupted. Will try to download again and try.
champikasam said:
Awesome ! Will check and let you know
---------- Post added at 04:39 PM ---------- Previous post was at 04:06 PM ----------
Could you check whether 800 x 480 img file is properly formatted ? I'm unable to mount or extract it. Getting an error saying the img file is corrupted. Will try to download again and try.
Click to expand...
Click to collapse
Full dropbox, check again...
Johny DJ said:
Full dropbox, check again...
Click to expand...
Click to collapse
Downloaded again. Same error
champikasam said:
Downloaded again. Same error
Click to expand...
Click to collapse
I extracted microg_preinstalled_800x480LP5.1.1rk3188.MTCB-C(20.8.2017) without problems ??
Try to rename it to some short name: update or something...
New link .rar
https://www.dropbox.com/s/95j1iqvqv...0x480LP5.1.1rk3188.MTCB-C(20.8.2017).rar?dl=0
Johny DJ said:
I extracted microg_preinstalled_800x480LP5.1.1rk3188.MTCB-C(20.8.2017) without problems ??
Try to rename it to some short name: update or something...
New link .rar
https://www.dropbox.com/s/95j1iqvqv...0x480LP5.1.1rk3188.MTCB-C(20.8.2017).rar?dl=0
Click to expand...
Click to collapse
Thanks ! i was able to download using the rar file. Most of the functions are working great ! It's fast and responsive. Please check on the following:
1) I'm unable to see the task bar/notification drawer at the top. I'm on the default launcher. Do i need to enable it anywhere ? Check the photos below:
https://ibb.co/hiJM1k
https://ibb.co/f24GZ5
2) I couldn't find google maps installed by default. So i installed the latest version from the play store. Its working fine (fast and responsive), but it doesn't show up in the selection list when i press the navi button on the player (to set it as the default navigation app). I only see the following nav apps in the list:
https://ibb.co/gG4YE5
Thanks !
champikasam said:
Thanks ! i was able to download using the rar file. Most of the functions are working great ! It's fast and responsive. Please check on the following:
1) I'm unable to see the task bar/notification drawer at the top. I'm on the default launcher. Do i need to enable it anywhere ? Check the photos below:
https://ibb.co/hiJM1k
https://ibb.co/f24GZ5
2) I couldn't find google maps installed by default. So i installed the latest version from the play store. Its working fine (fast and responsive), but it doesn't show up in the selection list when i press the navi button on the player (to set it as the default navigation app). I only see the following nav apps in the list:
https://ibb.co/gG4YE5
Thanks !
Click to expand...
Click to collapse
1. Hm...really don't know what happend to statusbar... try to disable / untick all xposed modules and reboot to see if some of xposed modules is cousing problems... I hope you did wipe all data / factory reset and then clear all and install from usb/sd and after that you can try wipe all data again and reboot, but everything should work because it's the same image from dsa's just added all the xposed modules...,
2. Yes, I forgot it, I updated image again and here: just copy folder in the rar with root explorer to system/app and change permisions just Maps.apk to r-r-w (664) reboot.
Try just to find your launcher in the android settings - apps and clear data.
Maps: https://www.dropbox.com/s/m44hv1189is36fr/Maps.rar?dl=0
Hello !
First I have to thank you @Johny DJ for this beautiful firmware. It's faster than i ever had on my MTCC-KLD6-V2.97 1024*600.
Also I take this opportunity to thank @dsa8310 and @Malaysk for their brilliant work in this adventure.
I love you guys, all as you are.
This said, i have a question : What's the difference between the first firmware (released 14/08 i think) that works really good on my unit RK 3188 (1024*600) and the release of today ?
Also my only "problem" is the text "null null" (like here : https://ibb.co/dL3dU5) on the screensaver which i think it correspond normally to the weather in Malaysk's rom. So i tried to install the weather app provided by Malaysk called "MTCWeather.apk" but it does not work. I have to precise that the display of the speed works OK.
Does this new release correct this little issue ?
Again thanks for all and have a nice day.
Cheers !
airlink75 said:
Hello !
First I have to thank you @Johny DJ for this beautiful firmware. It's faster than i ever had on my MTCC-KLD6-V2.97 1024*600.
Also I take this opportunity to thank @dsa8310 and @Malaysk for their brilliant work in this adventure.
I love you guys, all as you are.
This said, i have a question : What's the difference between the first firmware (released 14/08 i think) that works really good on my unit RK 3188 (1024*600) and the release of today ?
Also my only "problem" is the text "null null" (like here : https://ibb.co/dL3dU5) on the screensaver which i think it correspond normally to the weather in Malaysk's rom. So i tried to install the weather app provided by Malaysk called "MTCWeather.apk" but it does not work. I have to precise that the display of the speed works OK.
Does this new release correct this little issue ?
Again thanks for all and have a nice day.
Cheers !
Click to expand...
Click to collapse
Thank you!
There is no so much difference, just added new screen clock, but there will be still null null. It won't work because it's settings are part of android settings from Malaysk.
You should try lockclock apk (its related to weather app)
If you find a solution I can update system image to get weather fully working, but I was not bothering with that, because then system will also use more ram etc...I will try to remove the null null item...
here are the apps you can try:
https://www.dropbox.com/s/sukxg16l2z4ygbr/apps.rar?dl=0
Johny DJ said:
Thank you!
There is no so much difference, just added new screen clock, but there will be still null null. It won't work because it's settings are part of android settings from Malaysk.
You should try lockclock apk (its related to weather app)
If you find a solution I can update system image to get weather fully working, but I was not bothering with that, because then system will also use more ram etc...I will try to remove the null null item...
here are the apps you can try:
https://www.dropbox.com/s/sukxg16l2z4ygbr/apps.rar?dl=0
Click to expand...
Click to collapse
@Hal9k_'s MTCD ROM has a screen lock, I asked him how he did it and he said he just added back the original Android code.
EDIT : Lol, stupid me you said "lockclock" not screen lock ! Doh !

Categories

Resources