HI ALL,
I installed PA 3.99 for Samsung S2(9100) to experience Android 4.3.
But I found some issues,
1. The video call feature is missing.
2. If possible to disable Halo and PieControl, in fact, the screen side of 9100 is too small, these two attractive features will affect my input keyword and bring bad experience.
I saw some other ROM provides a enable/disable swtich for this....
3. Some other attractive Samsung device related features are not ported....is possbile to port them in this ROM, such as Swipe in call log(call or message), and Motion(all motion is not supported)
Hantsy
hantsy said:
HI ALL,
I installed PA 3.99 for Samsung S2(9100) to experience Android 4.3.
But I found some issues,
1. The video call feature is missing.
2. If possible to disable Halo and PieControl, in fact, the screen side of 9100 is too small, these two attractive features will affect my input keyword and bring bad experience.
I saw some other ROM provides a enable/disable swtich for this....
3. Some other attractive Samsung device related features are not ported....is possbile to port them in this ROM, such as Swipe in call log(call or message), and Motion(all motion is not supported)
Hantsy
Click to expand...
Click to collapse
Samsung apps can't be ported,as they require special Samsung framework,You can port only a few apps,like Note or Calculator.Swipe to call and Motion therefore will never be supported.
GamingDj said:
Samsung apps can't be ported,as they require special Samsung framework,You can port only a few apps,like Note or Calculator.Swipe to call and Motion therefore will never be supported.
Click to expand...
Click to collapse
Thanks for your explanation.
Personally I like the UI of PA 3.99(Android 4.3) and some apps, esp the new Gmail interface.
But it will loss any device specific features .
Regards
Hantsy
hantsy said:
Thanks for your explanation.
Personally I like the UI of PA 3.99(Android 4.3) and some apps, esp the new Gmail interface.
But it will loss any device specific features .
Regards
Hantsy
Click to expand...
Click to collapse
Yes....you can use a custom stock ROM,like Biftor ROM it can be customized in many ways.
If you want to report bugs, do that in the specific thread, so the developer can work on it. But first make sure if the problems are already know, or read the bug list. There's no need for this kind of thread
Related
Surface Dithering improves the quality of the images shown on the screen.
CM9 has the option to enable it. How can I do it on a Samsung ROM, if it's possible?
Doubt it. You have to understand, stock roms are built for ordinary phone users, not people like us. Ordinary phone users wouldn't even know what surface dithering is let alone what a setting to toggle it on/off does.
That's why you only see it in custom firmware.
I understand what you mean, but there are lots of mods and tweaks for a great multitude of Samsung ROMs, so... isn't there one that can enable surface dithering? It's a great feature which I'd like to have on my SII! :/
Oh, and I don't use a stock Samsung ROM, but a modified one (Omega v15).
Ask Indie if he can maybe include an option to toggle dithering in a future release of Omega ?
MistahBungle said:
Ask Indie if he can maybe include an option to toggle dithering in a future release of Omega ?
Click to expand...
Click to collapse
just edit your build.prop and add this line
persist.sys.use_dithering=1
it works on every rom but differences are negligable
I'm contemplating trading my GNex in for a S3 LTE. Was playing with a non-LTE S3 in the shop earlier and noticed the S3 has three dedicated buttons (one hard, two touch) on the bottom that roughly equals the GNex's "menu" (the house-shaped one), back and a funny third button that seems to activate the "options" within apps. JB/ICS has a built in app-switcher but I dont see this or some Samsung version of it in TouchWiz.
Question 1: if I were to install a custom ROM onto the S3, what would those three buttons do? I presume the "back" and "home" buttons would behave the same, would that funny upside-down "U" button then toggle the app-switcher?
Question 2: How does the S3's camera work on a custom ROM? Does it use the native camera app or is there a Samsung camera .apk that can be downloaded? If you use the JB native app, would the photo quality be the same as it would be on a regular S3 w/ the factory ROM? Do the custom ROMS have adequate drivers to support the full 8M and higher sensitivity? The GNex's crap camera is driving me nuts
Question 3: Perhaps the most important question; I want to move onto a custom ROM b/c Samsung's slow at updating their firmware, and also b/c I want to get rid of the customization that comes w/ the S3 (namely TouchWiz and what they've done to the notification/status bars + menus etc). Is there a way to do this w/o going to a custom ROM?
Sorry lots of questions, but the S3 suddenly looks a lot more restrictive than the GNex
ngmic said:
Question 3: Perhaps the most important question; I want to move onto a custom ROM .... Is there a way to do this w/o going to a custom ROM?
Click to expand...
Click to collapse
1. The buttons do Menu, home and back.
2. I haven't tried many camera apps but they all seem much the same, you will need to try it I suppose.
3. I am not sure if you got confused but I know I did!
You want to install a custom rom without installing a custom rom? No, I don't think you can do that.
http://forum.xda-developers.com/showthread.php?t=1674286
Rom Index ..
Button remain the same unless changed by the rom maker .
Camera the same if using Samsung based custom rom.
3 is impossible without using a custom rom .
You can flash stock Samsung firmware often before the update .
You can flash a custom rom with the standard ASOP Android interface .
jje
JJEgan said:
http://forum.xda-developers.com/showthread.php?t=1674286
Rom Index ..
Button remain the same unless changed by the rom maker .
Camera the same if using Samsung based custom rom.
3 is impossible without using a custom rom .
You can flash stock Samsung firmware often before the update .
You can flash a custom rom with the standard ASOP Android interface .
jje
Click to expand...
Click to collapse
Tks all for your help. Sorry the 3rd question was terribly written. What I'd meant to ask was whether there was a way to strip all the Samsung customization (mainly how they change the notification menu + settings menu appearance) w/o having to use a custom ROM?
@JJEgan, tks for that ROM index, it's most useful. Are you aware of any ROMs that actually change the menu button back to the "recent apps" screen? How can I get to that functionality within the stock factory ROM? HTC has a funky 3D switcher, does Samsung have something?
Mucho gracias
ngmic said:
Tks all for your help. Sorry the 3rd question was terribly written. What I'd meant to ask was whether there was a way to strip all the Samsung customization (mainly how they change the notification menu + settings menu appearance) w/o having to use a custom ROM?
@JJEgan, tks for that ROM index, it's most useful. Are you aware of any ROMs that actually change the menu button back to the "recent apps" screen? How can I get to that functionality within the stock factory ROM? HTC has a funky 3D switcher, does Samsung have something?
Mucho gracias
Click to expand...
Click to collapse
custom ROM = modification
what you seem to have requested...is to have modification to "strip all the Samsung customization"
so essentially...you will have to look into the option of custom ROMs.
do keep in mind that there are two main types of roms available...
Samsung based custom ROMs and Android Open Source Project (AOSP) ROMs.
Samsung based custom ROMs look virtually to be the same as the original one that you have on the phone when you first unbox it...but with small adjustments and tweaks to fix things that Samsung didnt fix, or forgot to fix...usually this means the same user experience but with better battery life, smoother UI transitions etc...generally further improving the same existing experience...
AOSP ROMs is totally different ROM experience in which many users are also interested in as it gives the user a more raw, more down to earth experience to Android...in addition, due to the fact that AOSP is more rudimentary in nature, it leads to faster rate of updates, fixes as well as modification due to the larger source tree as it relates to a wider range of AOSP compatible devices...
Galaxy Nexus is based on AOSP (without the Samsung Over-Lay) while this does typically mean a more leaner, low fat ROM, it does miss out on certain features such as in-box video playback, HDR camera functions, low motion high FPS camera functions, as well as other nifty and impressive functions...in which you would have actually paid the phone to do...
keep in mind...the Galaxy Nexus does have inferior hardware as far as most users will be concerned...
Samsung's "recent apps" can be shown by press and holding the middle physical button...
0semaj0 said:
custom ROM = modification
what you seem to have requested...is to have modification to "strip all the Samsung customization"
so essentially...you will have to look into the option of custom ROMs.
do keep in mind that there are two main types of roms available...
Samsung based custom ROMs and Android Open Source Project (AOSP) ROMs.
Samsung based custom ROMs look virtually to be the same as the original one that you have on the phone when you first unbox it...but with small adjustments and tweaks to fix things that Samsung didnt fix, or forgot to fix...usually this means the same user experience but with better battery life, smoother UI transitions etc...generally further improving the same existing experience...
AOSP ROMs is totally different ROM experience in which many users are also interested in as it gives the user a more raw, more down to earth experience to Android...in addition, due to the fact that AOSP is more rudimentary in nature, it leads to faster rate of updates, fixes as well as modification due to the larger source tree as it relates to a wider range of AOSP compatible devices...
Galaxy Nexus is based on AOSP (without the Samsung Over-Lay) while this does typically mean a more leaner, low fat ROM, it does miss out on certain features such as in-box video playback, HDR camera functions, low motion high FPS camera functions, as well as other nifty and impressive functions...in which you would have actually paid the phone to do...
keep in mind...the Galaxy Nexus does have inferior hardware as far as most users will be concerned...
Samsung's "recent apps" can be shown by press and holding the middle physical button...
Click to expand...
Click to collapse
Tks buddy. The gNex is by no means a weak phone (for 99% of the population) but certainly the camera and screen leaves much to be desired. Call quality is quite iffy too, maybe b/c its microphones are too sensitive; I take calls on the road and the caller hears every car, pedestrian and bus that goes back. Sure it has dual microphones that does some level of noise cancellation but doesnt do a whole lot of good. The iPhone (esp 5) smokes the gNex here.
I'm not wild about all the Samsung functions but certainly having a better camera app w/ HDR built in, Smart Stay etc is pretty appealing. Samsung-based ROM it is then, if only they could bring back the stock JB look and feel...the cyan/B&W layout is very sleek.
Anyone here tried the LTE version (I9305)? Carriers here in HK are offering it for free w/ an unlimited LTE plan for about US50 a month. Bit of a no-brainer when it's the same effective price as the I9300 w/ more RAM ) but I wonder if there will be less custom ROMs developed, and how LTE battery life compares? I'm not a massive data hog looking to stream videos regularly but I do have to VPN home every few days
why not remove the bloatware?
ngmic said:
Question 3: Perhaps the most important question; I want to move onto a custom ROM b/c Samsung's slow at updating their firmware, and also b/c I want to get rid of the customization that comes w/ the S3 (namely TouchWiz and what they've done to the notification/status bars + menus etc). Is there a way to do this w/o going to a custom ROM?
Click to expand...
Click to collapse
if you just want to remove the bloatware, have you considered simple rooting the stock firmware (not an upgrade and will block the samsung OTA update), then using a rooted explorer or adb or something (I personally use Titianium Backup to manage all my apps and backups) to delete the bloatware??
if you anything like me (who has been with android a while now) you'll have a set of 3rd party apps - so dont need the S Memo (love noteeverything) for example you can simple remove it from the phone. I did this for a few weeks before I moved to a custom ROM.
Heres a list of what is safe to remove...
https://docs.google.com/spreadsheet/ccc?key=0AqTvctlW89DtdC1qVUlLeVFTV3ZOdUtDclpBdVRQOUE&pli=1#gid=0
EDIT:i really need to change my signature...
Hi xda-community,
I would like to share my first (and extremly simple ) Xposed module with you.
This module allows you to slide before you have to draw/type in your security pattern/pin/whatever. It is particularly useful if you use CyanogenMod (or other ROMs, that allow App shortcuts in lockscreens) and want to use both shortcuts AND a security pattern/pin/whatever. It works similiar to HTC's Sense UI (3.x).
ROMs modified by manufacturers are known to have issues with this module (see below).
Code:
You install and use this module at your own risk!
I am not responsible for any damage it might cause to your beloved device!
Please note, that there is a sad bug present by using App shortcuts (in CM etc.) in lockscreen, which decreases the usability: You have to "unlock" your device with your pattern/pin/whatever twice. If you just unlock you don't have to do it twice. Therefore I rate this module as alpha. I would be very happy if someone has a solution to this problem .
Supported ROMs
TESTED and CONFIRMED WORKING:
AOSP:
- 4.3 (JellyBean)
- 4.4 (KitKat)
AOSP based:
- CM 10.2 (JellyBean 4.3)
Stock/OEM ROMs:
- Asus: 4.2 (JellyBean)
- Sony Xperia: 4.2 (JellyBean) - 4.4 (KitKat)
Should work on:
- 4.2+ (JellyBean) (lockscreen has been overhauled in 4.2, therefore no <= 4.1)
- 4.4 (KitKat)
- all AOSP based ROMs (CM, AOKP, Para, etc.) with Android 4.2+
Unsupported/problematic ROMs
ROMs modified by manufacturers are known to have issues with this module:
Samsung (TouchWiz):
- 4.2/4.3: simply does not work
- 4.4: has less issues, see http://forum.xda-developers.com/showpost.php?p=51980630&postcount=52
Credits
@rovo89 Your framework is amazing!
Known bugs
- Using app shortcuts causes you to "unlock" your device twice (see above)
- App shortcut to browser does not work (needs confirmation..)
How to use
1. Install Xposed framework as described here
2. Download and install XLockSecuritySlide via Xposed Installer (or see below)
3. Enable XLockSecuritySlide in Xposed Installer
4. Reboot and enjoy!
HELP ME!
If something went wrong (e. g. unlockable device) you can use the flashable Xposed recovery disabler ZIP (see attachment of that post!), which disables Xposed and therefore this module. After that you can safely disable/uninstall this module and re-enable Xposed again!
Download
Xposed repository (http://repo.xposed.info/module/de.stevolk.xlocksecurityslide)
OR
see attachments
Source code
Release under Apache License 2.0: github
Changelog
0.4 (2014/04/15)
Compatiblity with Sony Xperia ROMs (Thanks to @greg2001!)
0.3 (2014/01/29)
Fixed security mode bypass by pressing back button
Fixed "popup" security mode; it is the normal one now
0.2 (2014/01/28)
Fix for KitKat
0.1 (2014/01/27)
initial release
Will this work on a Samsung Galaxy S4 (TouchWiz based ROM)?
Joe0113 said:
Will this work on a Samsung Galaxy S4 (TouchWiz based ROM)?
Click to expand...
Click to collapse
I don't know it exactly, but I think it could work if Samsung hasn't heavily customized the lockscreen code. I do not have a way to test it out, so I would appreciate you testing it
Tested on Validus13 KK.....no go. Thanks for the work and sharing with the rest of us
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
not work on TouchWiz 4.3 on galaxy s4
badkill said:
not work on TouchWiz 4.3 on galaxy s4
Click to expand...
Click to collapse
No go on tw 4.3 Samsung s3
Sent from my SCH-I535 using Tapatalk
Damn!
Anyway you could make it work on TouchWiz (GS4; Android 4.3)?! @Stevolk
jasvncnt1 said:
Tested on Validus13 KK.....no go. Thanks for the work and sharing with the rest of us
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
KK fix released. Should work now. :cyclops:
Joe0113 said:
Damn!
Anyway you could make it work on TouchWiz (GS4; Android 4.3)?! @Stevolk
Click to expand...
Click to collapse
Well thats really sad... The problem is, that I do not have a Samsung device to test it out. Moreover it requires some work because TW is closed source. I will look at this, if I have enough time!
@Stevolk bro It is working fine:good: in my Xperia ZR running Stock 4.3 Jelly bean. but there is a small bug . The Xperia swipe screen is fine, but the pattern screen becomes black, I approximately need to draw the pattern in order to unlock the screen. But when I enable AOSP lockscreen using GEM Xposed module, both AOSP lock screen & pattern lockscreen is working fine :victory:. Thanks for you work. Screens attached for your info
Sorry for my bad English:angel:
Omg, thanks you so much , finaly someone made it, was missing this feature since gb !
(Nexus 4, 4.4.2)
Great module, works as expected on my HTC One X+ with CM11 android 4.4.2 but after switching to an other security while the module was active (from password to pin in my case) the phone soft rebooted upon sliding the slider again.
anthonythangaraj said:
@Stevolk bro It is working fine:good: in my Xperia ZR running Stock 4.3 Jelly bean. but there is a small bug . The Xperia swipe screen is fine, but the pattern screen becomes black, I approximately need to draw the pattern in order to unlock the screen. But when I enable AOSP lockscreen using GEM Xposed module, both AOSP lock screen & pattern lockscreen is working fine :victory:. Thanks for you work. Screens attached for your info
Sorry for my bad English:angel:
Click to expand...
Click to collapse
Hm.. it seems, that my module isn't compatible with OEM customized lockscreens, TouchWiz does also have issues. I updated the first post with this information.
If I have time, I'll have a look but it has low priority.
SerkSerk said:
Omg, thanks you so much , finaly someone made it, was missing this feature since gb !
(Nexus 4, 4.4.2)
Click to expand...
Click to collapse
I was annoyed, that no module existed with this functionality so I made one myself The only thing that isn't working correctly (except from compatibility with non-AOSP lockscreens like TouchWiz) is the double answering of security method if you use app shortcuts.
Ranomez said:
Great module, works as expected on my HTC One X+ with CM11 android 4.4.2 but after switching to an other security while the module was active (from password to pin in my case) the phone soft rebooted upon sliding the slider again.
Click to expand...
Click to collapse
Hm.. that is strange. I cannot reproduce this in AOSP 4.4.2 so far. Does it soft-reboot only one time after you switched the method or multiple times? Could you attach a logcat maybe?
0.2 does not work on LG Optimus G, stock 4.1.2 (bummer!), but works perfectly on Asus Memo Pad HD 7, stock 4.2.2 (yay!). Thanks a lot for this! Have been missing this feature since Disaster ROM on my previous SGS2...
kt-Froggy said:
0.2 does not work on LG Optimus G, stock 4.1.2 (bummer!), but works perfectly on Asus Memo Pad HD 7, stock 4.2.2 (yay!). Thanks a lot for this! Have been missing this feature since Disaster ROM on my previous SGS2...
Click to expand...
Click to collapse
Thanks for your feedback!
Any Android version below 4.2 is not supported because the lockscreen code has been heavily restructured in 4.2
Finally a stock ROM that works! :good:
Stevolk said:
Thanks for your feedback!
Any Android version below 4.2 is not supported because the lockscreen code has been heavily restructured in 4.2
Click to expand...
Click to collapse
Ahh, OK, I should have read the OP more carefully... Makes sense. Thanks!
Finally a stock ROM that works! :good:
Click to expand...
Click to collapse
I can only guess that's because Asus didn't make a lot of customizations to the vanilla Android -- some, but not much... For example, TouchWiz or Sense are way more heavily customized in every aspect. I can say that other Xposed modules that are originally designed for AOSP ROMs actually work much better on my Asus tablet than on other devices, like Samsung or LG (I am talking about stock ROMs).
Okay..big bug spotted
After swiping to get the pin/password/whatever if you hit the back button the security screen just disappears and the device is unlocked making the lock actually useless as it gets bypassed..
Can anyone else confirm this?
If so.. Dev please try to fix it ASAP
Sent from my Xperia S using Tapatalk
amey_gangal said:
Okay..big bug spotted
After swiping to get the pin/password/whatever if you hit the back button the security screen just disappears and the device is unlocked making the lock actually useless as it gets bypassed..
Can anyone else confirm this?
Click to expand...
Click to collapse
On my tablet, the on-screen Back button doesn't activate until the device is actually unlocked, so, no bug for me (can't bypass the lock screen). Could be different with hardware nav buttons...
Okay so apparently only the people with hardware buttons may see this happen
Sent from my Xperia S using Tapatalk
amey_gangal said:
Okay..big bug spotted
After swiping to get the pin/password/whatever if you hit the back button the security screen just disappears and the device is unlocked making the lock actually useless as it gets bypassed..
Can anyone else confirm this?
If so.. Dev please try to fix it ASAP
Sent from my Xperia S using Tapatalk
Click to expand...
Click to collapse
I found that happening on mine when I swiped across the camera then hit back to get out of it but I just tried swiping to get the pin then hitting back and it is unlocking like yours is. I'm on a Note 3 on 4.4.2.
thanks a lot for this
suggestion :-
when we slide then the secured lock comes in a box [See Screenshot 1]..can it be made to come in normal way [See Screenshot 2]
Hello Developer Team,
I absolutely enjoy using Paranoid 4.3 BETA3 on my Nexus 5. Performance is awesome and even the battery life improved by a lot in comparison to the stock ROM.
But there is one feature I really miss from my old S3 with OmniRom:
The possibility to easily switch between the notification drawer and the quicksettings by swiping the bar at the bottom.. Due to the large screen it is always a little struggle to reach the change button in the upper right position.
I hope you can consider to implement this feature, it would erase one of the last disturbing things in the ROM (for me)
Thanks and Greetings,
Fabian
This. I think this feature has been a feature that I have missed greatly on my Moto X.
Yes! I would love this feature too! Very useful!
+1 this feature would be awsome
Agreed.
Yes, would be very useful! :victory:
+1!
+1 too for this feature
+1
+1
stock-like simple features like that are always very welcome!:good:
I also think it's necessary
anexususer said:
+1
stock-like simple features like that are always very welcome!:good:
Click to expand...
Click to collapse
thats way far from stock like and its a hack
we're not implementing it EOS
ok.
But it still feels like something that could be a feature in 4.5 or 5.0, that was what I mean -designed for common android user-
For example 'immersive mode' or 'pie controls' are not stock-like experiences.
I don't mean that they are useless features, but they don't look very natural to me they look more like a 'hack' designed only for 'some' users.
That's my view though.
ayysir said:
thats way far from stock like and its a hack
we're not implementing it EOS
Click to expand...
Click to collapse
anexususer said:
ok.
But it still feels like something that could be a feature in 4.5 or 5.0, that was what I mean -designed for common android user-
For example 'immersive mode' or 'pie controls' are not stock-like experiences.
I don't mean that they are useless features, but they don't look very natural to me they look more like a 'hack' designed only for 'some' users.
That's my view though.
Click to expand...
Click to collapse
not happening
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