Guys please star the following issues .... and report further bugs here or at http://code.google.com/p/cyanogenmod/issues/list
[ Kindly follow their rules strictly about posting issues and post in the designed format only ]
How to take logcat :
http://wiki.cyanogenmod.com/wiki/Logcat
To support the CyanogenMOD devs in finding and fixing bugs, one should only
Install the official update-cm-7.2.0-RC1-cooper-signed.zip build (md5:da26c44f36032e202e7dd21c13bf14b7)
Install the official gapps bundle gapps-gb-20110828-signed.zip (md5:1647897d8ac3efb04723d2ad2c361a3f)
As disky already stated: Don't flash any third party kernels or scripts, if you wish to contribute and make error reports.
Also be aware that only the built-in Apps2SD is fully supported.
Consider to manually install apps you really need for the daily usage by hand, rather than by Titanium Backup or CWM-Recovery.
Take your time and add a logcat to every error report.
-----------------------------------------------------------------------------------------------------------------------------------------------
ISSUES :
1) Proximity sensor not working
http://code.google.com/p/cyanogenmo...etwork Owner Summary Stars Priority&start=200
2) Torch issue
http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
----------------------------------------------------------------------------------------------------------------------------------------------
Sent from my GT-S5830 using XDA App
Bugs
Guys
Please don't visit just report bugs to link as many as u can so that those bugs you r facing is to be corrected and as a result we get a official CM7 without any bugs.....
But in old one proximity is working I'm using it dude
Sent from my GT-S5830 using xda premium
shailpancholi said:
But in old one proximity is working I'm using it dude
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
u mean in nightly ??
I saw yesterday a video in which dolphin hd was recognicing speech through something called sonar but it seems not to launch when I shake it, neither when I press gesture button for a long time.
So I am wondering if its that sonar not supported by our phone or its just a bug on cm7
javiertury said:
I saw yesterday a video in which dolphin hd was recognicing speech through something called sonar but it seems not to launch when I shake it, neither when I press gesture button for a long time.
So I am wondering if its that sonar not supported by our phone or its just a bug on cm7
Click to expand...
Click to collapse
try that on all other unofficial cm versions available
Bug Hunter X
cyanogen said:
source: http://www.cyanogenmod.com/blog/cyanogenmod-7-2-0-rc1-is-upon-us
...
As usual, you can submit bug reports on these builds: if you find anything broken in your device while running CM7.2-RC1, (as downloaded from our mirrors or ROM Manager! Please do not submit reports if your build came from elsewhere), be sure to submit a report through http://code.google.com/p/cyanogenmod/issues/ , so that we can fix it in time for the final 7.2 release.
...
Click to expand...
Click to collapse
djsky2011 said:
unless you are using stock kernel, please don't report errors or bugs it's harder to fix
Click to expand...
Click to collapse
To support the CyanogenMOD devs in finding and fixing bugs, one should only
Install the official update-cm-7.2.0-RC1-cooper-signed.zip build (md5:da26c44f36032e202e7dd21c13bf14b7)
Install the official gapps bundle gapps-gb-20110828-signed.zip (md5:1647897d8ac3efb04723d2ad2c361a3f)
As disky already stated: Don't flash any third party kernels or scripts, if you wish to contribute and make error reports.
Also be aware that only the built-in Apps2SD is fully supported.
Consider to manually install apps you really need for the daily usage by hand, rather than by Titanium Backup or CWM-Recovery.
Take your time and add a logcat to every error report.
This measurements is solely there to minimize any interferences, which might come from sources other than from the RC1 build itself. I suggest further more, that if you seriously want to contribute and go on bug hunting, then please consider to refrain from any tweaking aside the already built-in tools and tweaks in CM7 itself.
Here is my current finding about the quickpanel (CM term: CyanogenMod settings->Interface->Notification power widget).
Problem:
If the "Toggle Mobiledata" widget is enabled and turned on, it will not turn off/on automatically, if the device is put into or revert from "Airplane mode".
How it should be:
Turn on WiFi and Bluetooth via Notification widget.
Put device into "Airplane mode".
WiFi and Bluetooth widgets will be automatically disabled.
Revert device from "Airplane mode".
WiFi and Bluetooth widgets will be automatically enabled again.
Can anybody reproduce the current "Mobiledata widget" behaviour above?
I would like to confirm this before filing a bugtracker report.
And remember: Don't blame anybody else but you, if the final release is coming and you're still wondering why on earth this or that bug isn't fixed yet!? ...
Btw, you have the possibility to rate a bug to raise its attention to the devs.
Thanks
PS:
Does anybody who has already played with CM7 know, how to checkout the current RC1 source build from github repo? I guess, if I simply only execute
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
then it will not be done, because then I can't see any tags like "CM7.2-RC1".
[x]
tossan: gah, just switched away from RC1 to test something else so can't double check for you :-( But can you check another bug: If you use toggle brightness on notification power widget -- the first time it is used I see the icon change as the brighness levels change on each click, but after one run through then the icon gets "stuck" on [A] auto icon even though the brightness does change. This is a minor visual glitch, not a functionality issue.
I think the branch for the final release is gb-release-7.2 -- but I don't know if the RC1 is taken from that (which is synced to gingerbread every so often) or from the gingerbread branch. I think CM uses branches and not tags, at least in the cooper repo that is the case. What I imagine is this: nightlies use gingerbread (the master branch), RCs are taken from nightly code, thus also gingerbread. When CM is ready to go from RC -> R they will push changes from gingerbread -> gb-release-7.2 ?
@iandol
Yes, I can confirm the little bug with the icon being stuck to stat_brightness_auto.png.
But while testing it, this are some more anoying visual glitches, which catch my eyes:
The brighness mode "Auto" doesn't seem to do anything at all. Disable the other modes and do long press the button and you will get into the normal "Settings->Display" menu, where you can set the brightness manually to any value. If you now press the toggle button, the brighness will not be auto set to any other value. I guess, that's because Cooper does not have a light sensor to begin with. And if I think about this further, I come to the assumption, this is maybe also the cause of the "stuck to auto brightness icon". ...
While toggling the buttons (not only the brightness one) the whole notification panel moves some pixels up and down.
Regarding the tag 7.2.0-RC1: It's here, where I've first seen it.
And here you can see the tag for CM-6.0.0-RC1.
I guess they're gonna do the same now for CM7.2 ?
Either the source for 7.2.0-RC1 is not publicly available yet or I just don't know how to get it out of the CM github. ...
[xXx]
The brightness menu problems and the vertical pixel jumping also affects the vo-1 KANG...
Your theory about why it sticks on auto is probably accurate, though are you sure cooper doesn't have a light sensor?
tossan said:
Either the source for 7.2.0-RC1 is not publicly available yet or I just don't know how to get it out of the CM github. ...
[xXx]
Click to expand...
Click to collapse
It is as vo-1 appears to have built it. I think they use the master branch, and once they are RELEASE only then they'll tag, the tag you mention (if you look at branches/tag github menu ththat git tag doesn't exist) is just the name given to the changelog:
https://github.com/CyanogenMod/andr...mmit/c90ca3ae7a24cd24e4637c145d49712a99264ed6
iandol said:
Your theory about why it sticks on auto is probably accurate, though are you sure cooper doesn't have a light sensor?
Click to expand...
Click to collapse
Otherwise I can't imagine of a good reason why Samsung disabled this feature in their GB builds.
iandol said:
It is as vo-1 appears to have built it. I think they use the master branch, ...
Click to expand...
Click to collapse
Normally the master branch corresponds to the newest android release. In AOSP that would be currently ICS. Who knows? CM does many things different than AOSP. And I guess vo-1 isn't very interested in sharing his secrets, how he has managed to build from CM7.2-RC1. ...
[xXx]
I think there are two "master" branches, one for gingerbread and one for ics. Each will probably split of finished branches and get tagged appropriately. vo-1 uses the gingerbread branch AFAIK and the cooper repo from teamhacksung and its derivatives (Pablo is at least one). I think his English is non-existant which is why he doesn't post here much, and my Russian ain't too hot. He is not fishing for donations and does at least quote his sources unlike the other 7.2 build so I'll give him the benefit of the doubt on his intentions...
Reading around about light sensor, you're right; I'm amazed Samsung skipped on such a dirt cheap sensor (photodiode is as cheap as air! ;-))
iandol said:
I think there are two "master" branches, one for gingerbread and one for ics. Each will probably split of finished branches and get tagged appropriately. vo-1 uses the gingerbread branch AFAIK and the cooper repo from teamhacksung and its derivatives (Pablo is at least one). I think his English is non-existant which is why he doesn't post here much, and my Russian ain't too hot. He is not fishing for donations and does at least quote his sources unlike the other 7.2 build so I'll give him the benefit of the doubt on his intentions...
Reading around about light sensor, you're right; I'm amazed Samsung skipped on such a dirt cheap sensor (photodiode is as cheap as air! ;-))
Click to expand...
Click to collapse
The master branch is for the lastest OS they're working on.....
So the master branch is currently ICS .
And as for a GB "master" branch.....my finger points toward gingerbread or gingerbread-release .
Herpderp Backflip.
CM7.2-RC1 source found
Okay, just had a little chat over #cyanogenmod and got the confirmation, that 'gingerbread' is the RC1 branch I'm looking for.
I'm a bit confused, because my expectation before was that the instructions to build CM from source would be for stable builds only. ...
Anyway, many thanks to henkpoly and nebkat to clear this one out!
(11:57:26 AM) henkpoley: what I get from http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit is that development (gerrit patches) is done against 'gingerbread' (the one you checked out)
Click to expand...
Click to collapse
[xXx]
is it true updated vo-1 based from official ?
anyone with battery report ?
Powered by CM7 + Tea
tossan: any other useful news like who will maintain cooper (i.e. submit bugfixes to gingerbread branch!) on IRC?
Digital compass is broken, just wanted to check on the beautiful conjugation of Venus and Jupiter in the sky tonight using google sky map, and no compass data to update my orientation, double checking using GPS essentials and no compass data. 14.03RC1
Can anyone else confirm broken compass before I place bugreport?
tossan: can confirm your mobiledata widget failing to toggle on airplane mode toggle. However:
1) after toggling airplane mode ON then OFF:
2) I cannot now toggle mobiledata manually, icon is permanently ON
3) toggle airplane mode back ON
4) I can manually toggle mobiledata icon OFF.
Logcat shows this every other click manually (when I don't see the icon change, something does happen, isDataConnectivityPossible goes from false to true):
Code:
I/TelephonyRegistry( 281): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=apnSwitched interfaceName=null networkType=3
I/TelephonyRegistry( 281): notifyDataConnection: state=1 isDataConnectivityPossible=true reason=apnSwitched interfaceName=null networkType=3
D/Tethering( 281): pdp0 is not a tetherable iface, ignoring
I/TelephonyRegistry( 281): notifyDataConnection: state=2 isDataConnectivityPossible=true reason=apnSwitched interfaceName=pdp0 networkType=3
W/Tethering( 281): attempting to remove unknown iface (pdp0), ignoring
I/TelephonyRegistry( 281): notifyDataConnection: state=0 isDataConnectivityPossible=true reason=dataDisabled interfaceName=pdp0 networkType=3
D/NetUtils( 281): failed to remove default route for pdp0: No such device
D/GTalkService( 363): ##### Network broadcast (connected=true) type=mobile, state=DISCONNECTED
D/GTalkService( 363): [GTalkConnection.1] ### networkStateChanged: active and curr network type/state are the same(1/CONNECTED), ignore
I/TaskReceiver( 522): action = android.net.conn.CONNECTIVITY_CHANGE
D/Tethering( 281): MasterInitialState.processMessage what=3
D/Tethering( 281): MasterInitialState.processMessage what=3
I/MediaUploader( 1046): No need to wake up
I/TaskReceiver( 522): action = android.net.conn.CONNECTIVITY_CHANGE
D/GTalkService( 363): ##### Network broadcast (connected=true) type=WIFI, state=CONNECTED
D/GTalkService( 363): [GTalkConnection.1] ### networkStateChanged: active and curr network type/state are the same(1/CONNECTED), ignore
D/CMStats ( 1300): CONNECTIVITY_ACTION: noConnectivity = false
I/MediaUploader( 1046): No need to wake up
D/CMStats ( 1300): CONNECTIVITY_ACTION: noConnectivity = false
I/dalvikvm( 392): Jit: resizing JitTable from 512 to 1024
iandol said:
tossan: any other useful news like who will maintain cooper (i.e. submit bugfixes to gingerbread branch!) on IRC?
Click to expand...
Click to collapse
Sorry, but no. I was already happy enough to be able getting hold of the RC1 source at last. ...
Looks like all accepted bugs are assigned to retired CM member coolya/Kolja. But honestly, it doesn't really matters to me, if only in the end the reported bugs do somehow get fixed. But yeah ... it would also be nice to know the name of our patron. And it would be great, if his name is the same one, who has brought Cooper to CM! ...
iandol said:
Can anyone else confirm broken compass before I place bugreport?
Click to expand...
Click to collapse
Yes, I can confirm it (tested with Phone Tester, GPS Test and Smart Compass).
Regarding the impossibility to turn of the MobileDataWidget manually: I can't reproducce your test case. In my case, it just takes a little longer from the first touch until the MobileDataWidget goes into disabled mode.
Proximity sensor doesn't work even on custom kernel - zImage - Mod v1.5.
1) Random Capacitive button lights turn on
2) Torch
bugs are solved with it.
(Just saying, in case someones willing flash custom kernel to get rid of current bugs.)
tossan said:
Okay, just had a little chat over #cyanogenmod and got the confirmation, that 'gingerbread' is the RC1 branch I'm looking for.
I'm a bit confused, because my expectation before was that the instructions to build CM from source would be for stable builds only. ...
Anyway, many thanks to henkpoly and nebkat to clear this one out!
[xXx]
Click to expand...
Click to collapse
Did you ask about gingerbread-release ? My guess is that it's RC0 .
Herpderp Defy.
Related
VibraFix forces the haptic feedback to stop.
On some devices, when you uncheck the haptic feedback option in settings, vibrate stills enabled for some keys.
This app is useful for people who are annoyed with this, in my point of view, bug.
It's also allways a good idea to deactivate haptic feedback in order to save some power juice.
How does it work ?
VibraFix stops totaly the vibrate with a rude and simple method : changing the permission (777 to 444) for the vibrate ressource.
Features :
Vibrafix forces vibrate to stop.
VibraFix can be started automaticaly at boot.
VibraFix is a quiet application running in the background and uses very little resources.
VibraFix can enable again the vibrate when a phone call or/and a SMS is received.
There is also an attempt to deal with the vibrate when an AlarmClock is trigged.
Optional notification in order to enable/disable vibrate in one click.
Devices concerned :
This fix has been tested only on Motorola Defy (stock ROMs android 2.1 and android 2.2.2)
but should certainly works also on other phone devices/ROMs with the same bug.
According to stats, VibraFix is installed and used on :
Motorola devices ~80% : Motorola Defy, Motorola Milestone2, Motorola Atrix, Motorola Droid I & II
but also : Samsung Galaxy S2, Samsung Galaxy Mini, Samsung Galaxy Ace, HTC Evo 4G, leo
Donations :
VibraFix is FREE to use - and without ads.
My aim is really not to earn money : I have made this app for myself first.
However, if you think VibraFix is useful for you, Paypal donations are welcome to support me.
Share and publish this app cost me the price of a google android market account and several hours of working ....
I can also understand, you don't want to donate for a fix so just increase the thanks'O'Meter on this forum or/and increase rating in Android market .
It's free and make me happy !
Thanks for supports, and feel free to post in that thread : report any bugs or suggest improvements you want.
Thanks to bobbyphoenix for convincing me to make this thread and for people who have already said thanks.
Feedback is always welcome.
Permissions :
WARNING : The application must have ROOT rights. : in order to change system files permissions
Also there are some permisions needed :
android.permission.VIBRATE : in order to test vibrate and vibrate on SMS received.
android.permission.READ_PHONE_STATE : in order to detect a phone call
android.permission.RECEIVE_SMS : in order to detect a SMS received
android.permission.RECEIVE_BOOT_COMPLETED : in order to enable the app at phone booting (autostart)
com.android.launcher.permission.INSTALL_SHORTCUT : in order the user can create a shortcut for fast enable/disable VibraFix
android.intent.action.ACTION_POWER_CONNECTED,android.intent.action.ACTION_POWER_DISCONNECTED : in order to manage "In charge" option.
I know all these permissions can be sensible that's why the source code is shared (link in the post).
Download :
From android market or use the QRbarcode in this post.
Screenshot :
in this post or from here and here.
Notes :
+ When roots rights are disabled, VibraFix is useless and its options are disabled.
Other links :
Initial post for the app on xda forum : here (73 downloads/views before link removed).
Interested discussion about the "feature"/bug on motorola forum here.
Sources codes are shared here (if someone is interrested).
You can register to this RSS to follow bug fixes or next features (this topic will be updated too).
Sorry for my english.
Known bugs :
+ Vibrate on AlarmClock option works only on some AlarmClock (stock Android AlarmClock and Motoblur AlarmClock).Version 1.3.1 tries to add more Alarm app triggers.
+ Disabling vibrate after an AlarmClock is done only after 10 minutes and not when the alarm is killed by user.
How to report a bug
Post on this forum a description of the issue, and give me options you use with that form :
Code:
version : XXXXXX
[X] Enable Vibrafix
[ ] Enable Vibrate
----------------------------
[ ] Auto-start
[ ] StatusBar notification
----------------------------
[ ] On phone call
[ ] On SMS
[ ] On alarmclock
----------------------------
[ ] In "Pocket Mode"
[ ] Not in charge
[ ] In vibrate mode
----------------------------
[ ] Silent mode
[ ] Vibrate mode
[ ] Normal mode
Changes log :
v1.6.2 (2015/09/26)
Add option for enable VibraFix only when phone is in vibrate mode (request from Nurio in that post)
v1.6.1 (2015/04/11)
- "In charge" Option implemented in an another approach.
v1.6 (2015/04/06)
-Add option to only enable vibrate when device is not charging
v1.5 (2014/03/12)
-"Pocket mode" option added.
v1.4.1 (2014/01/18)
- fixe issue with autostart option
- change minor settings (default options, text)
- add android.permission.ACCESS_SUPERUSER permission in manifest
v1.4 (2013/10/22)
+ add tab compatibility adempt
+ add options to enable Vibrafix according to phone status.
v1.3.3 (2013/07/24)
+add the possibility to create separate shortcuts for switching on or off VibraFix
v1.3.2 (2012/12/19)
+ add the possibility to create a shortcut to enable or disable VibraFix.
v1.3.1 (2011/06/24)
+ add a bunch of Alarm Triggers : stock 2.3 Deskclock, HTC worldclock, Nexus AlarmClock, Samsung alarmclock.
v1.3 (2011/06/13)
+ minor GUI changes.
+ add optional notification support
+ add support from android 1.6
+ first realease on android market
v1.2 (2011/06/10)
+ add enable vibrate option for Motoblur Alarm Clock.
+ a minor performance fix
v1.1 (2011/05/31)
+ add new icons
+ add enable vibrate option for SMS
+ fix button for trying vibrate (for android 2.2.1)
+ fix a bug in settings registration
+ topic dedicated to the app in xda forum
+ SVN links shared
v1.0 (2011/04/2011)
+ public release on xda forum
v0.9 (2011/03/2011)
+ initial release (beta for personal using, on android 2.1)
History :
I have got my Defy in the end of February 2011 with android 2.1.
I really dislike the haptic feedback. So my first try was to uncheck option about it in phone settings.
Bah ... still enabled ! I have searched for a solution and was surprised to find NOTHING.
hmmm... Coz I have some JAVA knowledge, I decided to code a solution for that : my first android application, VibraFix was born.
I really thought this application will be useless after the official update (android 2.2.1) ...
but nothing changed and I still use my fix.
Thanks again!!! You really made my day.
Thanks ill test it out
Sent from my MB525 using XDA Premium App
Any chance for a new version that will run under Froyo?
I have Froyo for about half an hour and missed it from the very first minute.
Christian72D said:
Any chance for a new version that will run under Froyo?
I have Froyo for about half an hour and missed it from the very first minute.
Click to expand...
Click to collapse
I'm running the official 2.2.1, and it's working for me. If you just upgraded to FroYo you probably lost root. Even if you have the Superuser Icon you have to root again.
Christian72D said:
Any chance for a new version that will run under Froyo?
I have Froyo for about half an hour and missed it from the very first minute.
Click to expand...
Click to collapse
bobbyphoenix said:
I'm running the official 2.2.1, and it's working for me. If you just upgraded to FroYo you probably lost root. Even if you have the Superuser Icon you have to root again.
Click to expand...
Click to collapse
I'm on official 2.2.1 too and the fix works fine.
Bobbyphoenix is certainly right ...
Also last time I upgraded to 2.2.1, I have noticed a bug in settings saving when losing root rights, but I think I have solved this bug in the last update.
When root rights are disabled, the application should reset all options to the default ones : mean vibrate is enabled again ...
So don't forget to check settings of the app after rooting your phone again.
I added my initial post about that in a new part called 'notes'.
But if still not work, uninstall VibraFix and install it again.
... and If still not work, repost here, I will inspect the code in that case.
(in fact even if that works, you are welcome to repost here to say it ty ).
Hi! Thank you for the great app. Its working perfectly but can you integrate in future versions options to enable/disable vibration for integrated alarm?
hi krisberck, thanks for feedback.
Concerning the feature you want, I'm sorry but I think it's not possible to do.
The thing you call 'integrated alarm' is not a part of android system but in fact an another application.
As an external app, no system trigger can be detected.
Perhaps there is an idea to solve that : find a way to detect notification about the Alarm Clock App in the status bar.
At the moment, I don't know if it's possible but I will search for that.
Thank you for your quick replay. I will search and if i found i will tell you immediately.
Forget my previous post. It's possible.
I found how to enable the vibrate when the Motorola Alarm is ringing.
Now, need to find a trigger when the Motorola Alarm is killed ...
Just a question of time...
And for this last issue, if it's really impossible to find, there are some ideas to bypass the problem : a timer or a specific amount of vibrations before disable again the vibrate.
Cool! If you don't find another way except timing you could set it for about 10min. It would be enough I guess even for the people that have hard to wake up and snooze the alarm couple of times. Thanks again!
Sent from my MB525 using XDA App
updated to version 1.2.
Changes log :
v1.2 (10th June 2011)
+ add enable vibrate option for Motoblur AlarmClock.
+ a minor performance fix
Click to expand...
Click to collapse
Option for AlarmClock is limited :
- works with a timer to disable the vibrate (10 minutes).
- works only for Android Stock AlarmClock and Motoblur AlarmClock.
Added a 'known bugs' section in initial post.
Cynyx said:
updated to version 1.2.
Option for AlarmClock is limited :
- works with a timer to disable the vibrate (10 minutes).
- works only for Android Stock AlarmClock and Motoblur AlarmClock.
Added a 'known bugs' section in initial post.
Click to expand...
Click to collapse
Awesome! Thanks!
Thank you very much to implement this function for the alarm clock! You are the best!
updated to version 1.3
Changes log
v1.3 (2011/06/13)
+ minor GUI changes.
+ add optional notification support
+ add support from android 1.6
+ first realease on android market
Click to expand...
Click to collapse
Excellent work again and congratulations for android market upload! I hope that many defy users will easily find your app to fix this bug witch is found on all original roms.
krisberck said:
Excellent work again and congratulations for android market upload! I hope that many defy users will easily find your app to fix this bug witch is found on all original roms.
Click to expand...
Click to collapse
you mean that in custom roms, there's no such vibration (bug)?
account1 said:
you mean that in custom roms, there's no such vibration (bug)?
Click to expand...
Click to collapse
I'm not 100% sure but for what a read i never found solution for custom roms that are based on official roms. For custom roms that are completly defferent from motorola roms - like CM7 or MIUI maybe it fixed. Until VibraFix only one solution exist - completely disable the vibrations. I never found such automatic way
finally i fixed the vibration frenzy, 10x for this app !
great app, haptic feedback is really annoying most of the time. Works great on BB 1.55!
GUMMY
Gummy ROM is made for speed, stability and to stay as closely in line with AOSP as possible while still supporting a large amount of devices and giving you all of the features you love. It isn’t slowed down by features you’ll never use nor is it so slim as to be just another AOSP build.
Features:
* New base built from AOSP
* Status Bar Mods
* Theme Manager
* Hardware Key Mod
* Lock Screen Mod
* Many Wallpapers
* Performance Control
* Application Permission Controls
* Carrier Label Options
* Background Style
* Lock clock widget
Instructions for installations:
**Use whatever recovery, so long as it's 4.4 compatible**
1. Download ROM
2. Download Gapps
3. Push to sdcard
4. Reboot Recovery
5. Wipe Data and Cache
6. Install ROM
7. Install Gapps
8. Reboot System
Contributions:
* Thank you to Cyanogenmod for device and hardware repositories. Without this, porting Gummy to QCOM devices would have been nearly impossible.
* Thank you to Google for the best source code.
* androidfilehost.com for hosting our file servers!
Team Members: In alphabetical order
Primary Developers:
Cphelps76, Kejar31
Developers and Device Maintainers:
arrrghhh, Bkjolly, BytecodeMe, DHacker27, Hashcode, NoCoast, Papi92, TDM, Xoomdev
Artwork direction and development
ChadFrankos, Cphelps76, Kejar31
Github- https://github.com/TEAM-Gummy
Gerrit- review.gummyrom.com
Twitter- @gummyRom
Gummy-M2.0-04-29-14-UNOFFICIAL-mondrianwifi.zip
Gummy-M2.0-05-12-14-UNOFFICIAL-mondrianwifi.zip - 205.08 MB
Reserved
Greetings - I found this ROM runs quite well, and has some nice options.
Still having some odd keyboard issues - gesture typing doesn't display, although works. Long press on keys also work, but similarly nothing is displayed (other than the kb dimming)
Enjoy!
arrrghhh said:
Greetings - I found this ROM runs quite well, and has some nice options.
Still having some odd keyboard issues - gesture typing doesn't display, although works. Long press on keys also work, but similarly nothing is displayed (other than the kb dimming)
Enjoy!
Click to expand...
Click to collapse
That's a CM problem which will likely just magically fix itself when I fix it for CM unless you want to fix it first and then send it back my way...
crpalmer said:
That's a CM problem which will likely just magically fix itself when I fix it for CM unless you want to fix it first and then send it back my way...
Click to expand...
Click to collapse
Thanks for the info mate. I hope I can actually start to help a bit here now that I'm tearing into the device.
You've done a great job tho, without the CM trees none of these other ROM's would even boot!
arrrghhh said:
Thanks for the info mate. I hope I can actually start to help a bit here now that I'm tearing into the device.
You've done a great job tho, without the CM trees none of these other ROM's would even boot!
Click to expand...
Click to collapse
No problem. I really wanted an 8" tablet with an msm8974 processor and this was all there was, but, man, Samsung doesn't do software.
Thanks for the offer to help (hopefully that was a general offer!). I think I've fixed this specific problem, just waiting on a build on another device to make sure I didn't somehow screw it up (unfortunately, the fix is in packages/inputmethods/LatinIME so the change will affect all devices).
I don't see a download link for gapps. Any pictures? Coming from an other ROM which -local- way is suggested to restore data like mail settings if I do not use cloud services? TB?
guidogsbn said:
I don't see a download link for gapps. Any pictures? Coming from an other ROM which -local- way is suggested to restore data like mail settings if I do not use cloud services? TB?
Click to expand...
Click to collapse
Feel free to use whatever gapps you wish. CM's, PA's 0-day...
I spose I can take some screenshots.
Mail settings... I never really figured out how to transfer, at least not for my corporate email. For gmail, well that's simple. For my corporate email, I had to re-setup the account every time... I couldn't figure out how to backup the settings with TB even. Just a user/pass and the server... so I guess not a big deal, but a bit annoying.
Rom runs real well. I use it all the time...Video recorder does not work: "HFR not supported.." Not that important. Any solution?
Moa1480 said:
Rom runs real well. I use it all the time...Video recorder does not work: "HFR not supported.." Not that important. Any solution?
Click to expand...
Click to collapse
Interesting. I need to rebuild with all the changes, I can't seem to keep up with crpalmer .
I will rebuild and let you know if a fresh build exhibits the same behavior. I assume you are clean flashing?
arrrghhh said:
Interesting. I need to rebuild with all the changes, I can't seem to keep up with crpalmer .
I will rebuild and let you know if a fresh build exhibits the same behavior. I assume you are clean flashing?
Click to expand...
Click to collapse
Yes clean flashing. Sould add that other cameras than standard save video recordings.
New build in the OP, new host as well.... my old hosting is going away.
I found the camera would take video from the back cam, if you turned it down to 720p. Also, the vid cam that comes with the 'full' PA Gapps package seems to work fine, although I couldn't find a resolution setting there.
Keyboard etc fixes from crpalmer baked in.
arrrghhh said:
New build in the OP, new host as well.... my old hosting is going away.
I found the camera would take video from the back cam, if you turned it down to 720p. Also, the vid cam that comes with the 'full' PA Gapps package seems to work fine, although I couldn't find a resolution setting there.
Keyboard etc fixes from crpalmer baked in.
Click to expand...
Click to collapse
New build works well. Vid cam from the new Google cam also works well.
Any chance you will develop a ROM for the T321?
or SM-P900?
Sent from my SM-P900 using Tapatalk
TabLife said:
Any chance you will develop a ROM for the T321?
Click to expand...
Click to collapse
canezila said:
or SM-P900?
Click to expand...
Click to collapse
Sorry folks, I don't blind build. I only develop for devices I own, which I can test on.
However, if there is CM then other ROM's can fairly easily be ported. Just a matter of someone with the device stepping up.
In the correct device area for 'just' the 12.2, there isn't much. I haven't seen CM yet. But I would like to someday build or port and help out others with the 12.2.
Are these builds still going?
bigmike35 said:
Are these builds still going?
Click to expand...
Click to collapse
Well, this ROM actually ran really well - but there didn't seem to be an ounce of interest, everyone wanted SlimROM at the time.
I spose now that it's official I will start building Gummy again if there's interest...?
arrrghhh said:
Well, this ROM actually ran really well - but there didn't seem to be an ounce of interest, everyone wanted SlimROM at the time.
I spose now that it's official I will start building Gummy again if there's interest...?
Click to expand...
Click to collapse
I am interested lol, well I just got the tab so just trying to find roms, see whats out there and how things are going. Any kernel support for asop/cm build roms? (Besides the stock kernel thats built in)
I am a crack flasher so if you need things tested or something just let me know!
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
(Official) Downloads - Download the rom, gapps and other addons.
MondrianWifi downloads:
Archive:
Slim-mondrianwifi-4.4.2.build.5.4-UNOFFICIAL-20140528-2305
Slim-mondrianwifi-4.4.2.build.5.4-UNOFFICIAL-20140529-0951
Slim-mondrianwifi-4.4.3.build.5.7-UNOFFICIAL-20140609-0914
Slim-mondrianwifi-4.4.4.build.5.10-UNOFFICIAL-20140624-1709
Slim-mondrianwifi-4.4.4.build.6.6-UNOFFICIAL-20140721-1012
Slim-mondrianwifi-4.4.4.build.6.9-UNOFFICIAL-20140729-0821
Slim-mondrianwifi-4.4.4.build.7.4-UNOFFICIAL-20140822-1723
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
Contributors
@crpalmer
SlimRoms
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Bugs
Bluetooth won't enable... seems permissions related?
As usual, this wouldn't be possible without all the hard work from @crpalmer and the CM team in general.
In fact he already did most of the bringup for Slim, so apologies for dragging on this one - I know people were waiting for it.
Enjoy! I am thinking I can keep up with the weekly schedule Slim does, I'll try to coordinate my builds with their weeklies as best I can.
Let me know!
OK, audio was easily fixed... just needed to add audio-caf
Other issues are still present.
Good news! Thank you very much for bringing SlimBean to us! ☺
Sent from my SM-T320 using Tapatalk
Awesome. Of course this drops right as I'm heading out of town and can't flash, but that's how my life goes. If you're not sure you've got the right repo and such, ask the guys in the N5 thread. They often help people trying to make their own builds. Friendly bunch there. Thanks for your work on this (and of course crpalmer!).
From my Pro Tab 8.4
arrrghhh said:
OK, audio was easily fixed... just needed to add audio-caf
Other issues are still present.
Click to expand...
Click to collapse
JaylanPHNX said:
Awesome. Of course this drops right as I'm heading out of town and can't flash, but that's how my life goes. If you're not sure you've got the right repo and such, ask the guys in the N5 thread. They often help people trying to make their own builds. Friendly bunch there. Thanks for your work on this (and of course crpalmer!).
From my Pro Tab 8.4
Click to expand...
Click to collapse
See the post I quoted, it's fixed.
I've also fixed the keyboard issue... I guess I should play with different values, but the values used for CM didn't work... default is 4, crpalmer adjusted to 5... which worked for other ROM's. I just tried 15 for fun, and it worked.
Going to attempt 6 and see if that is good enough. I'm not sure what the negative effect would be of turning up this divider tho?
I finally got a chance to flash this and though I haven't tested everything possible, so far I've not encountered a single issue. I'm just thrilled to death. It's just like on my Nexus 5. I can't thank you, @arrrghhh (and of course @crpalmer for his device wizardry) enough.
From my Pro Tab 8.4
Can't turn on bluetooth
I can't turn on bluetooth. I don't know if I did anything wrong.
xpdragon said:
I can't turn on bluetooth. I don't know if I did anything wrong.
Click to expand...
Click to collapse
I can confirm, Bluetooth will not turn on. As I said earlier, haven't tested everything yet.
From my Pro Tab 8.4
xpdragon said:
I can't turn on bluetooth. I don't know if I did anything wrong.
Click to expand...
Click to collapse
JaylanPHNX said:
I can confirm, Bluetooth will not turn on. As I said earlier, haven't tested everything yet.
From my Pro Tab 8.4
Click to expand...
Click to collapse
I've never used BT on my tab, never saw the need...
I'll try it later. Thanks for the report.
I would never use it either if it weren't for my MOGA controller and Dead Trigger 2.
Sent from my Slim Nexus 5 with smoothness by Faux.
arrrghhh said:
I've never used BT on my tab, never saw the need...
I'll try it later. Thanks for the report.
Click to expand...
Click to collapse
If using the Tab for WiFi calls (Groove IP, &c), Bluetooth becomes a useful feature to have.
Sent from my SM-N900P using Tapatalk
Seems pretty smooth, but holy cow is the status bar tiny. It's a good thing I'm not elderly.?
Sent from my SM-T320 using Tapatalk
micmars said:
If using the Tab for WiFi calls (Groove IP, &c), Bluetooth becomes a useful feature to have.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I didn't say it was useless, I just didn't see a need for it.
Also, isn't GrooveIP basically dead now that Google removed support for third parties?
I wish Hangouts was as good on Android as it was on iOS... sad really. But I digress, I'll look at the issue...
manigault said:
Seems pretty smooth, but holy cow is the status bar tiny. It's a good thing I'm not elderly.?
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
lol, Slim likes to use a different DPI. I believe Slim is working towards a DPI updater on-the-fly... otherwise you'll have to adjust it in the build.prop.
No Doubt...
arrrghhh said:
I didn't say it was useless, I just didn't see a need for it.
Also, isn't GrooveIP basically dead now that Google removed support for third parties?
I wish Hangouts was as good on Android as it was on iOS... sad really. But I digress, I'll look at the issue....
Click to expand...
Click to collapse
Understood as to your statement of its utility, inasmuch as one person's feature is another's bloat. As to Groove IP rendered dead, it was given another span of life via the entity Ring.to. Swift to establish, and a host of additional numbers to grab. Works flawlessly.
I as you am dumbfounded by the superior quality of Hangouts for iOS.
Thanks for all you do.
arrrghhh said:
lol, Slim likes to use a different DPI. I believe Slim is working towards a DPI updater on-the-fly... otherwise you'll have to adjust it in the build.prop.
Click to expand...
Click to collapse
I've never messed with Dpi before, but you learn something new every day. Lookin good now!! Thanks!!
I've noticed apps seem to treat the tablet as though it has a menu button. No three dot button in UI or menu button appears in soft keys. Is there a build.prop edit or something that can fix this?
From my Pro Tab 8.4
All I want for Christmas is a rom on the 10.1...
SomeGuyDude said:
All I want for Christmas is a rom on the 10.1...
Click to expand...
Click to collapse
And it may take till Christmas to get one. The Exynos processor in it makes it harder to work with, from what I understand. The 8.4 has the better supported Snapdragon 800 and is not too different from the Note 3.
From my Pro Tab 8.4
Update: This effort is currently on standby. Abhinav finally released an update for his original builds. I will probably start building again if Abhinav disappears for a while. I'm currently considering creating alternative CWM builds. Till then, use this[Well Abhinav didn't update his ROM for 2 weeks now bringing out a new nightly
What is Carbon?
CarbonRom is an aftermarket firmware based on the Android Open Source Project.
We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, AOKP, and anyone else we may have borrowed commits from that hasn’t been mentioned here. If you feel you have been unfairly left out, please – let us know.
Bugs:
CM11 bugs
Reboot to recovery does not work
Clock/Battery icons in recovery constantly flash on and off
Click to expand...
Click to collapse
Steps to install
1. Clear Data, cache, and dalvik cache in recovery
2. Flash the zip
3. Flash GApps (optional)
If you are coming from a previous version of carbon
1. Clear cache and dalvik cache in recovery
2. Flash zip
3. Flash 4.4.3 GApps (if applicable)
Credits:
@Abhinav2 For kernel
@alwaysadeel For helping with every query I had, and the CarbonDevXperia repoes
@ XperiaSTE for device trees
Download link
Download Links:
18 June Nightly
21 June Nightly
Changes:
Reverted to CWM 6.0.4.8 to remove flashing battery and clock in recovery
Updated to Android 4.4.4 KTU84P
12 July Nightly
Changes:
Latest Carbon
CWM -> TWRP
MuffinIsCute said:
Download Links:
18 June Nightly
Click to expand...
Click to collapse
thanks !!! hav been waitin for a long time :good: wil report after i try
MuffinIsCute said:
Download Links:
18 June Nightly
Click to expand...
Click to collapse
some features lik d small calling pad wen screen is unlocked is missing!! rom is good!! good work :good:
MuffinIsCute said:
Download Links:
18 June Nightly
Click to expand...
Click to collapse
Congrats on your first self built Rom
I believe I can release a 4.4.4 version soon.
Very good rom... No issues so far! :thumbup:
Congratulations but i think kernel source is needed? Correct me if i am wrong please.
Sent my AOSP Xperia P
AndroidNoob69 said:
Congratulations but i think kernel source is needed? Correct me if i am wrong please.
Sent my AOSP Xperia P
Click to expand...
Click to collapse
You're right. I took all the repoes from CarbonDev and CarbonDevXperia with the exception of the device tree. The kernel was taken from CarbonDevXperia.
I shall be including a build guide anyway.
amazing ROM wid stock kernel .....
and every things working fine ......
and slide notification i love that and carbon consist multiple feature ....... that user can change easily.....
but after screen go to sleep ...... the red light is blinking
sammyroid said:
amazing ROM wid stock kernel .....
and every things working fine ......
and slide notification i love that and carbon consist multiple feature ....... that user can change easily.....
but after screen go to sleep ...... the red light is blinking
Click to expand...
Click to collapse
Tats called pocket mode!! u can switch it off in settings--->>>lockscreen
and slide right n find pocket mode in 2nd o 3rd tab!! in 1st tab it'l already be off so move to 2nd or 3rd tab n check!!
------------------------------------------------------PRESS THANKS IF IT WAS USEFUL---------------------------------------------
is there any way to move app in kitkat to the sd card
@MuffinIsCute- bro can u add tat cm11 launcher to carbon so tat we can make d icons small...wen we use dpi to reduce icon size it becomes a bit conjusted n ugly!! or is der a way tat u can point me to???
vicky2131 said:
@MuffinIsCute- bro can u add tat cm11 launcher to carbon so tat we can make d icons small...wen we use dpi to reduce icon size it becomes a bit conjusted n ugly!! or is der a way tat u can point me to???
Click to expand...
Click to collapse
There is an app on the Play Store that can download many CM apps, including Trebuchet. I believe the app is called CM Apps.
https://play.google.com/store/apps/details?id=com.maartendekkers.cmapps
Oh and regarding the small calling pad you were saying was missing
The feature (OmniROM's non intrusive callUI)was removed from Carbon on 17 June since it was freezing up the currently open app. It was replaced by Slim's non intrusive CallUI, which is not enabled by default. To enable it go to Dialer -> settings and enable incoming call in background.
In Slim, this will just put the call in the notification bar and to access it you'd need to pull it down, but when combined with Hover, it takes on a life of its own, and behaves very similarly to the OmniROM one, but without the freezes.
This is why I love Carbon: The features randomly thrown together interact in beautiful ways.
MuffinIsCute said:
There is an app on the Play Store that can download many CM apps, including Trebuchet. I believe the app is called CM Apps.
https://play.google.com/store/apps/details?id=com.maartendekkers.cmapps
Oh and regarding the small calling pad you were saying was missing
The feature (OmniROM's non intrusive callUI)was removed from Carbon on 17 June since it was freezing up the currently open app. It was replaced by Slim's non intrusive CallUI, which is not enabled by default. To enable it go to Dialer -> settings and enable incoming call in background.
In Slim, this will just put the call in the notification bar and to access it you'd need to pull it down, but when combined with Hover, it takes on a life of its own, and behaves very similarly to the OmniROM one, but without the freezes.
This is why I love Carbon: The features randomly thrown together interact in beautiful ways.
Click to expand...
Click to collapse
Thanks for ur reply bro!!! was very helpful!! :good: n pressed thanks too
Really nice rom with the perfect set of features. I'm especially fond of lockscreen notifications, as it's one of the most useful things ever imo.
No dialer lag at all after a day of usage.
Nice battery life.
Thanks for bringing this to our device! :thumbup::thumbup:
Found a little bug
Just found a little bug I'd like to report to contribute a little:
When music is played and the home button is pressed, the played track stops and the main volume is set to default and volume has to be toggled a few times to revert that.
Also, the track names aren't scrolling in neither the widget or notification drawer.
Nothing too serious but worth sharing.
Tried it with Apollo and Sony Walkman app
Catlog attached or available online here.
EDIT:
Found the culprit. It was a restored Nova launcher backup which seemed to have messed up. No trouble with media playback since another setup of Nova was done!!!
panecondoin said:
Just found a little bug I'd like to report to contribute a little:
When music is played and the home button is pressed, the played track stops and the main volume is set to default and volume has to be toggled a few times to revert that.
Also, the track names aren't scrolling in neither the widget or notification drawer.
Nothing too serious but worth sharing.
Tried it with Apollo and Sony Walkman app
Catlog attached or available online here.
Click to expand...
Click to collapse
Strangely I was unable to replicate the bug. Where did you get your Apollo and Walkman? I'll test with those too.
panecondoin said:
Just found a little bug I'd like to report to contribute a little:
When music is played and the home button is pressed, the played track stops and the main volume is set to default and volume has to be toggled a few times to revert that.
Also, the track names aren't scrolling in neither the widget or notification drawer.
Nothing too serious but worth sharing.
Tried it with Apollo and Sony Walkman app
Catlog attached or available online here.
Click to expand...
Click to collapse
No problem wid my apollo!! i too tried and everythin works fine...
vicky2131 said:
No problem wid my apollo!! i too tried and everythin works fine...
Click to expand...
Click to collapse
Um is Apollo already available out of the box? For me it isn't, I pulled it off a backup.
Also which nightly are you using?
Download link is in the thread, do not use the "Download" section in XDA DEVDB, my network has some problems with it for now.
After nearly one year's silence, SwipeBack is now back alive, known as SwipeBack2.
SwipeBack2 is the continue of SwipeBack. It has still the basic feature, swipe-to-return gesture, inspired by the library SwipeBackLayout written by @ikew0ng(a.k.a. IssacWong, 碎星iKe, 碎iKe). It provides a smooth, nature-like and highly customizable swipe-to-return gesture. This module is initially a wrapper of SwipeBackLayout in Xposed, and was welcomed widely by Xposed users. Gradually it has gained much new features that is more than SwipeBackLayout.
If you have installed the old SwipeBack, please uninstall it first, and then you can install SwipeBack2
Features:
* Swipe-to-return gesture
* Per-activity settings which means you are able to customize settings on <strong>each page of each app</strong>
* Experimental hacks for Lollipop (may not work, use with caution, do not turn it on globally)
* More experimental features are coming in future releases.
Note that SwipeBack2 is now only a rewrite and a port to Lollipop (but it still works on ICS/JB/KK). It has many work to-do, as:
* Pure-gesture mode (disable scrolling effects, enables compatibility with apps that consist of Fragments but not Activities, and can work with Browsers)
* Fully-costomizable trigger area (at <strong>any</strong> position on the edge, to fix compatibility with apps that has a gesture like drawers already)
* Automatic bug report and crash log submitter
* More (<strong>advices are always welcome)
SwipeBack2 is free software released under the terms of GNU GPLv3. Source code available at https://github.com/PaperAirplane-Dev-Team/SwipeBack
Changelog
1.0.2:
- Fix icons
- Add ability to show a settings shortcut to the current app activity in notif bar
This is a minor release. We will go to fix several bugs in the next few weeks
1.0.1:
- Fix crashes in main app UI
- Fixes for apps with wallpaper
Downloads
From Xposed Store: http://repo.xposed.info/module/info.papdt.swipeback
From Google Play Store: https://play.google.com/store/apps/details?id=info.papdt.swipeback
FAQs:
Q: Why renamed to SwipeBack2?
A: Because SwipeBack2 is completely rewritten, and is refactored to have a better stability and flexibility. And another reason is, that SwipeBack (us.shandian.swipeback) is blacklisted by Alipay because of the unsecure SwipeBack, so I just renamed it to SwipeBack2 (info.papdt.swipeback), hoping that it will not be blacklisted any more.
Q: Would you add feature X / fix bug X?
A: Feel free to send emails or open issues on GitHub page. I may not have time to reply to you all, but I will take a look at bug reports and feature requests and have the resonable ones implemented in new releases.
Q: SwipeBack is great! Do you accept donations?
A: Well, not now.
XDA:DevDB Information
SwipeBack2, Xposed for all devices (see above for details)
Contributors
PeterCxy
Source Code: https://github.com/PaperAirplane-Dev-Team/SwipeBack
Xposed Package Name: info.papdt.swipeback
Version Information
Status: Beta
Created 2015-03-31
Last Updated 2015-03-31
Crashes when loading the app, gets to about 80% then fc
Edit: logcat https://www.dropbox.com/s/jikihl6rkfijgiu/logcat_and_device_info.zip?dl=0
Not for me, works as it should. Everything fine. Just have to experiment a bit with the Lollipop Feature, few Apps don't like it as stated in the App.
Ty!
apps loaded well but cannot change settings any of the app "unfortunaly swipeback 2 has stopped" please fix it
using in note 2 phantom 13 ROM
Cannot get it working on a Nexus 5 with CM12, I don't know if I'm doing anything wrong but I don't think so. Just installed, enabled it on Xposed and restarted. It's not CAF, so it may be fault of the rom. What android and rom are you using?
EDIT:
Just disabled every other module and it's working now. I will try to find which one is causing the problem and report it because it may be useful to someone.
Works fine expect one bug - on Lollipop when I go to the task manager after swipe back an app it shows the launcher screen as the thumbnails for the swiped back app.
Works great on LG G2 XenonHD 5.0.2:good:
Fantastic Modul, easy to use. Just awesome. Thank you.
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_190900.mp4
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_184109.mp4
Galaxy S5 G900F CM12 Fusion ROM
good to see new version thanks for continuing this module
Sent from LG Optimus G
Im glad someone revived this amazing module ... please keep it updated ... i will keep giving feedback and any bugs if i find on this thread
Edit 1 Bugs-
1. While swiping back on Whatsapp it goes back perfectly from the Chat screen to the Chat list. But while Swiping back on other apps like Gallery or Instagram. It doesnt swipe back. It goes to Home Screen.
2.After Swiping back the Recent app page shows wrong thumbnails .. it shows the Home screen as thumbs instead of App last state. (Screenshot Attached)
3.Also after restart i got a com.location.google has stopped ... i may have said the term wrong .. but it was something regarding Location.
4. SB2 force closes if Global settings option is pressed.
Notes:
I have unistalled old Swipeback and Freshly Installed this.
I love this app and will continue to send feedback to make it best.
--
Kitkat - LG G2 D802 International Model - Stock Firmware.
Been waiting for this module to work, thx for it. Unfortunately there are some bugs, the Gmail animation is fine but the rest are broken with in the status bar, like in the video https://vimeo.com/123755651 (nexus 4 stock 5.0.1 and Franco kernel) . Keep up the good work
nicholes said:
apps loaded well but cannot change settings any of the app "unfortunaly swipeback 2 has stopped" please fix it
using in note 2 phantom 13 ROM
Click to expand...
Click to collapse
Same here...;/ (and I know logcat or gtfo
can anyone confirm if it is working on kitkat or not(mine dont work)
Expect the called bugs, great app!
crash at loading apps and breaks recent app menu
nicholes said:
can anyone confirm if it is working on kitkat or not(mine dont work)
Click to expand...
Click to collapse
it runs fine on my Nexus 5 running the latest SlimKat
For us new to this... What does it do?
Simply swipe to go back to the screen you were at previously?
HorstiG said:
Fantastic Modul, easy to use. Just awesome. Thank you.
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_190900.mp4
https://dl.dropboxusercontent.com/u/73964661/SCR_20150331_184109.mp4
Galaxy S5 G900F CM12 Fusion ROM
Click to expand...
Click to collapse
What is that widget you use? I attached a snip of it.
DeisNet said:
Been waiting for this module to work, thx for it. Unfortunately there are some bugs, the Gmail animation is fine but the rest are broken with in the status bar, like in the video https://vimeo.com/123755651 (nexus 4 stock 5.0.1 and Franco kernel) . Keep up the good work
Click to expand...
Click to collapse
Same here :/
Moto G 5.0.2
mcdavid said:
What is that widget you use? I attached a snip of it.
Click to expand...
Click to collapse
Hi, thats Zooper Widget Pro, Handmade