I won't post the link here because I don't have permission to do so, but a couple of the developers from Cyanogenmod have been working on Alpha builds, and a new one (4.4.4) was released last night sometime. The following link is to the dev's G+ page so go ahead and find the link from there, not too hard.
https://plus.google.com/+TomMarshall/posts
Also, APN's are working along with LTE speeds, haven't tested out phone calls yet due to no vibration/sound anywhere in the device, so it's not really "usable" at this point. The newest SlimROM Gapps work just fine by the way.
Hopefully we can keep this thread as a central point for discussion since now there are multiple spread throughout the General and Q&A forums.
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
pside15 said:
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
Click to expand...
Click to collapse
Well, even if there is, that doesn't do any good for the casual user flashing this ROM, they won't hear/feel a phone call/message if the phone is in their pocket. Even if everything besides sound/vibration is working, I still like my phone to act like a phone, you know?
pside15 said:
Are you sure there is no sound period? I thought there was sound through the earpiece just not the external speakers.
Click to expand...
Click to collapse
I'm on the 09/07 build and I have sound through the earpiece, calls seem to work fine.
Edit: Headset sound works as well.
stevew84 said:
Well, even if there is, that doesn't do any good for the casual user flashing this ROM, they won't hear/feel a phone call/message if the phone is in their pocket. Even if everything besides sound/vibration is working, I still like my phone to act like a phone, you know?
Click to expand...
Click to collapse
Yeah, I understand. Was just wondering if I had read the info correctly before.
kchino said:
I'm on the 09/07 build and I have sound through the earpiece, calls seem to work fine.
Click to expand...
Click to collapse
That's all well and good, but I have to have a phone that notifies me of a call/text while it's sitting on my desk or in my pocket. I fully appreciate the fact this is an Alpha build and I'm not complaining in the least bit, I just can't wait until 5.0 hits the G3...or at least 4.4.4 stable with a good 5.0 theme.
If anyone is wondering this ROM is actually based off Slim as opposed to CM. It has Slims Recents, Quicktiles, Floating Window, Shake Events etc, which are all working.
kchino said:
If anyone is wondering this ROM is actually based off Slim as opposed to CM. It has Slims Recents, Quicktiles, Floating Window, Shake Events etc, which are all working.
Click to expand...
Click to collapse
This is what I don't get, given the fact that this is a PHONE, I would assume that the first thing to get working correctly would be any and everything relating to calls/texts.
Uh...well, everything gets tested and built from the ground up. So some things come along faster than others.
mzrdisi said:
Uh...well, everything gets tested and built from the ground up. So some things come along faster than others.
Click to expand...
Click to collapse
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
The "phone" part of the build does work correctly. The audio not working is a separate matter that has nothing to do with the "phone" part of the rom.
While audible notifications are most certainly a requirement for a daily driver, the reality is that these are alpha builds that are being worked on by a select few people. Everything will get worked out, it's just a matter of time. Been here in this very place several times with phones before the G3, unless you're in the know how, you just gotta play the waiting game
cvsolidx17 said:
The "phone" part of the build does work correctly. The audio not working is a separate matter that has nothing to do with the "phone" part of the rom.
While audible notifications are most certainly a requirement for a daily driver, the reality is that these are alpha builds that are being worked on by a select few people. Everything will get worked out, it's just a matter of time. Been here in this very place several times with phones before the G3, unless you're in the know how, you just gotta play the waiting game
Click to expand...
Click to collapse
Yea i know, been thinking about trying to learn how to go about compiling a CM build from scratch, or port from something similar, but that's a lot of time and effort.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
I'm not sure why you have a gripe at all? It's a very stable alpha build that is actively being worked on and provided to you for free! If you don't like the pace of development why don't you contribute? I understand that you opened this thread to discuss AOSP builds but contrary to your assertion that you are "not complaining" you've posted some inaccuracies about the 1st and only AOSP ROM and told us over and over how you need your phone to be a phone.
We get it. Go back to the LG ROMs until this one suits your needs.
kchino said:
I'm not sure why you have a gripe at all? It's a very stable alpha build that is actively being worked on and provided to you for free! If you don't like the pace of development why don't you contribute? I understand that you opened this thread to discuss AOSP builds but contrary to your assertion that you are "not complaining" you've posted some inaccuracies about the 1st and only AOSP ROM and told us over and over how you need your phone to be a phone.
We get it. Go back to the LG ROMs until this one suits your needs.
Click to expand...
Click to collapse
I'm simply responding to people here, I pointed out what works and what doesn't work with the TWO working Alpha builds. There is a third in the works by AICP but has yet to be released. My only gripe really is for a build to be released, although a test build, without the main functionality of the device working properly...that's it.
I am on an LG ROM at the moment.
The purpose of this thread is to discuss the builds as they come out and to have a central location for all prominent links.
stevew84 said:
I know, my whole gripe with test/alpha build is that getting the phone part of the device isn't necessarily a priority upon releasing something.
Click to expand...
Click to collapse
The thing is a lot of those things aren't phone specific so if they work on other builds they should work here.
For anyone who has tried this, does it get rid of the artificial sharpness?
GoogleAndroid said:
For anyone who has tried this, does it get rid of the artificial sharpness?
Click to expand...
Click to collapse
It looks fine, I mean I don't notice any over sharpening, but then again I don't have my face less than a few inches away from my eyes. Either way, the animation scale is set to .5 so it looks faster than it really is. Set the scales back to 1.0 and everything is really fluid with NO skipping/stuttering/whatever you want to call it.
Lack of vibration and sound across the board is really the only issue at this point. For day to day use, I mean.
Still waiting on the AICP build as that will probably incorporate the missing necessities that the other two builds are lacking.
stevew84 said:
This is what I don't get, given the fact that this is a PHONE, I would assume that the first thing to get working correctly would be any and everything relating to calls/texts.
Click to expand...
Click to collapse
Correct you don't get it. The source code for the ROM is already done, it already has their features. What they are doing is adding the device source and trying to get the drivers working. Its not like they think well lets go add 1% battery, its already in the source code. What they are working on is the device side not the feature side.
stevew84 said:
It looks fine, I mean I don't notice any over sharpening, but then again I don't have my face less than a few inches away from my eyes. Either way, the animation scale is set to .5 so it looks faster than it really is. Set the scales back to 1.0 and everything is really fluid with NO skipping/stuttering/whatever you want to call it.
Lack of vibration and sound across the board is really the only issue at this point. For day to day use, I mean.
Still waiting on the AICP build as that will probably incorporate the missing necessities that the other two builds are lacking.
Click to expand...
Click to collapse
I'm not sure why you continue to mislead based solely on your preference. I'm on the build right now, it is easier to state what doesn't work because this build is very close to beta:
1.2 09/07 build - Not working:
External Speaker (...On the back, Headset audio and earpiece audio are working fine.)
Vibration
Cameras & rear LED
External SD Card
Bluetooth
I haven't come across anything else that isn't working. Wifi, Mobile Data, GPS, incoming/outgoing calls have worked without a hitch. Also this is AOSP so there is zero of the text sharpening that is present in the LG ROMs. I've changed the governor to interactive by default it's set to performance and the cpu does not scale which will contribute to heat reports that initially popped up.
kchino said:
I'm not sure why you continue to mislead based solely on your preference. I'm on the build right now, it is easier to state what doesn't work because this build is very close to beta:
Not working:
External Speaker (...On the back, Headset audio and earpiece audio are working fine.)
Vibration
Cameras & rear LED
External SD Card
I haven't come across anything else that isn't working. Wifi, Mobile Data, GPS, incoming/outgoing calls have worked without a hitch. Also this is AOSP so there is zero of the text sharpening that is present in the LG ROMs. I've changed the governor to interactive by default it's set to performance and the cpu does not scale which will contribute to heat reports that initially popped up.
Click to expand...
Click to collapse
Mount to PC works for you? I mean internal storage.
Sent from my LG-D851 using XDA Free mobile app
Related
Full credit goes to Ssserpentine, SpaceMoose, and OldMacnut for their work on their united efforts to port Honeycomb to our tablets! It seems they are no longer working on it so I decided to create this thread and see what we all could to do together to improve what they have given us!
The point of this thread is to find ways to gather anyone with knowledge on developing, even if its just the "lowly 7-Zippers" like me, to see how we can remove minor bugs and small issues from the ROM. I know Oldmacnut was going to pick it up, but he has a lot on his plate right now and he has been in pain and is more interested in finishing the CM7 Port instead. I respect his decision, but so many people want honeycomb working on our tabs. So I am turning to the dev community here to see if we can group together and fix things in this rom together. If we cant solve the major bugs, lets address all the little things, cuz the little things add up.
Spacemoose made a list of suggestions from users earlier on how to solve minor issues, and little workarounds, but I would like to see if there is a way to roll up those fixes into one full updated ROM flashable through a zip/odin/heimdall file, and see if we can come up with more. You can see this post here, but I have added them to the second post as well in a more organized form.
Some Useful Links as Well:
SpaceMoose's Github
6-19-11 Apps Confirmed Working on [CDMA] / [GSM] Honeycomb Alpha 2.5
Currently Known Bugs:
CDMA
A) Red Border Around Screen at Random Times
B) Constant Gallery Force Close
C) Stock Launcher hangs for many seconds at a time randomly
D) SD Card Does Not Mount
E) Youtube app does not work
F) Orientation Sensor is not functional
G) Honeycomb thinks Device Keyboard is enabled by default
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
I) HQ Youtube does not work (LQ does on the mobile site)
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
K) Flash Player is not Fully Functional
GSM - Please Submit or confirm if the above bugs are the same and/or you have different ones!
Red - Signifies an issue that is unaddressed or has not been solved yet.
Orange - Signifies a Temporary Fix or Workaround is mentioned in the post I linked to.
Blue - Will signify a temporary fix or a work around that we have been able to include in a flashable file
Green - Will signify a bug that has been completely fixed in a flashable file.
------------------------------------------
Lets put our minds together and see what we can do guys! Btw this was inspired by Rodderik's thread [SPRINT][CDMA]Galaxy Tab (SPH-P100) Mega Development Starter Thread (CWM, EF17 TAR), so if youre interested in this, you might like his thread too!
Current Workarounds/Temporary Fixes:
Letters correspond to the bugs listed in the OP.
A)
Ssserpentine:
1) Open up Dev Tools
2) Go to Development Settings
3) StrictMode Visual Indicator - turn it off
4) back out of app and now open it again.
5) If this doesn't get rid of MOST of the red borders, REBOOT and open app again.
Click to expand...
Click to collapse
B)
anfalas:
"Get Gallery3D to play nice by going into settings, applications then 'Clear Data' - works great, can change wallpaper etc. Only downside is it has to be done each reboot....."
Click to expand...
Click to collapse
C)
Ssserpentine:
“WANT IMPROVED UI, LESS RED BORDERS, LESS FC'S AND SCROLLING AND SOFT KEYS THAT PLAY NICER? Try adw launcher. for some reason just having it installed helps just as much as using it.”
Click to expand...
Click to collapse
D)
mattman83:
"to mount UMS if you have no external SD then use the below line. Same changes as above... echo /dev/block/mmcblk0p1 > /sys/devices/platform/s3c-usbgadget/gadget/lun1/file"
Click to expand...
Click to collapse
or
corodius:
"if you have an external sd, by extending the commands to: su mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard/ mount -t vfat /dev/block/mmcblk1p1 /mnt/sdcard/external_sd/ This will mount the cards the way they are originally mounted in the samsung/overcome roms."
Click to expand...
Click to collapse
E)
Use m.youtube.com to play LQ videos
Click to expand...
Click to collapse
F)
ztag100:
"If you download barcontrol from the market, you can set it so that a notification links to the rotation app, thus when the notification is clicked it will change the orientation."
Click to expand...
Click to collapse
G)
"one way to load keyboards On the language/keyboard settings page, turn physical keyboard to "no" or "off" or something like that. Now when on a text field, you should see a small keyboard tray in bottom right corner.."
Click to expand...
Click to collapse
H) ---
I) ---
J) ---
K) ---
----------------------------
Submit a New Bug or Fix:
Please submit bugs using the color coded system I explained in the OP. If you are submitting information on solving a bug please address the bug by the corresponding letter so that we can stay organized and know what youre talking about. If you have a new bug please check the OP to make sure I havent listed it, then post it on here and dont worry about the letter, I will alphabetize them. Of course I will credit you in the OP for any fixes or workarounds you may find! Good luck to us all!
Reserved as well!
Yes, please
I would really love a Honeycomb ROM for the Galaxy Tab. There are many reasons why I want to put Honeycomb onto the original Galaxy Tab.
Just see the difference for yourself: Blank space, single pane, one-category-at-a-time menus in Gingerbread
VS.
Less blank space, concise, dual pane interfaces in Honeycomb.
Gingerbread apps are just designed for smaller smartphone screens, so they look too big and spaced-out on the 7-inch Galaxy Tab for my taste. I would really love to see some tablet-optimized apps on the Galaxy Tab!
-------------------------
And yes, I respect the developers and appreciate them so much for the time they put into making custom roms a reality for us!
Please make the thread for GSM also.
TheATHEiST said:
Please make the thread for GSM also.
Click to expand...
Click to collapse
Are the bugs the same? Or are there others that I havent mentioned? I will try to make a section for both tabs if theres different bugs in each one.
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Still, hope is eternal, I suppose
PunkRock said:
Why no mention of ssserpentine?
In op or thread tittle?
He worked on the GSM version.
Moose did the major part of the port and the cdma version.
That other person stumbled, or so he claims, on a audio fix. Never saw a release of this apparent audio fix.
Wonder how many donations he got on open thread with no release posted.
Hmm.
Makes ya wonder why that thread is even there.
Dole out the credits properly.
Just know it needed to be said, and go ahead and get mad. Truth hurts.
alot of angry responces coming, maybe, but dare ya to point out a single lie in this post. Even an exaggeration.
Moose did hc for MONTHS and noone offered any valid help, except ssserpentine, why do you think anyone is gonna get off their but now?
Why don't you, punkrock?
Cause I know how utterly hopeless this task is.
Why don't you all just wait for the leak of the next os?
That so much closer than some random Joe, or Joe's on xda getting hc ported at this point .
is the dead horse braised yet?
Click to expand...
Click to collapse
Easy man, in my frenzy of trying to organize the thread, I forgot to credit Ssserpentine in the OP, youre right he did contribute a lot, no need to be rash, I will update it right now.
EDIT: btw oldmacnut did make an audio fix, im running his rom right now, I downloaded it when he had it posted before he took it down, and Im sure some of the bugs I mentioned are fixable on the rom level rather than through adb. My goal wasnt to debug the rom completely, it was to incorporate all the existing bug fixes and workarounds into one rom, while possibly solving others. Also the GSM devs are aplenty here, while we barely have any CDMA, Im sure we have enough talent to make it better than what it is. It might not be flawless, but Im sure we can squeeze more functionality out of it.
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
oldmacnut said:
Its weird,
Honeycomb is more or less froyo based, obviously as we had hc long before gb, so at the time when I started getting into this whole dev thing hc/froyo seemed just different to me.
But after working on the abortion called gingerbread, and working onbthe kernel stuff, froyo to me, is starting to look like a much more viable and dev friendly option.
Alot if the work Dan did in hc was from scratch, or from the sdk, etc. The audio fix I did was from both.
The big issue on getting hc up and going into a usuable rom is source, we really really need that source for hc. Otherwise, its going to be a long drawn out road of trial and error building with alot of these issues never really getting fixed.
Truth is,
No device with our hardware exists with hc, so no drivers that we need.
We need Google to release the hc source.
I liked hc on my tab just like y'all, but.......I know its just a novel weekend fun toy till we get better resources.
Sent from my SCH-I800 using xda premium
Click to expand...
Click to collapse
Yeah I know, the lack of source sucks along with the fact we dont have drivers. I dont think we'll have everything working anytime soon at all, if ever even, but I think some of the minor annoyances like the disappearing quick settings toggle, sdcard mounting issues, and graphical errors can be solved without that kind of stuff. Me personally, Id just like HQ Video Playback and 3D Graphics working a hundred percent along with orientation, but as you said no drivers so idk how easy that'd be. Still, Im sure we could solve some of these minor issues. I keep browsing over the Nook Color Forums trying to find hints to solving some of these things
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
BulletproofIdeal said:
GSM Tab here I'll flash the old 2.5 alpha release and confirm these bugs, see what else I can do.
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
Nice to see something happening here. I love my Tab but would like some advancements in OS to address specific issues. I am very new to the dev side of the Android OS but would like to get involved.
--Mike
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
On a different note, the alpha 2.5 HC Rom for gsm, the sd cards will not mount no matter what, I've tried The terminal and the mount instructions many times all I am able to do is get the tab to recognize my external sd as the internal sd, and if you try to go to settings applications and clear data for the gallery you get a force close as soon as you tap manage applications
Sent From Githrog's Tab
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
Githrog said:
What blows my mind is that they have created an almost perfect HC port for the $150.00 walmart sold viewsonic g-tablet by means of the flashback roms so why is it so hard to get HC working on our tabs? And why can't someone just dump the Rom from the gtab10.1 and use that as a starting point?
Click to expand...
Click to collapse
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Honeycomb is closed source. Nobody can make a tablet without Google's blessing. The reason given is that Honeycomb was rushed out the door, and the code isn't good enough for an open source release. They're right you know, setting the emulator to anything smaller than a tablet will result in about a million force closes. Honeycomb just isn't as supportive of hardware as Gingerbread was. To save developers the headache of supporting a platform that wasn't ready, Android's openness got shelved.
Luckily this is going to change. The big cheese said so himself on the Official Android Developers blog, "This temporary delay does not represent a change in strategy. We remain firmly committed to providing Android as an open source platform across many device types." Source code is coming back. This will make the modding community's life much easier. Cyanogenmod 8 (I got excited just typing that) and Ice Cream Sandwich will be able to get hacked onto just about anything.
Click to expand...
Click to collapse
CROrION said:
Guys, there is no reason to develop honeycomb, it is inposible to make fully functional honeycomb rom, wait a month or less for ICS, read this (quote from android police posted today):
Click to expand...
Click to collapse
I just wanted an excuse to try out Honeycomb
BulletproofIdeal said:
Ok done some immediate testing on my GSM Tab for some of the known issues
A) Red Border Around Screen at Random Times
Confirmed
Solution: is the same as the CDMA
B) Constant Gallery Force Close
Confirmed
Solution: Cannot be fixed through Setting, crashes as soon as you try to Manage Applications
C) Stock Launcher hangs for many seconds at a time randomly
Not really was slow on boot but no major problems
D) SD Card Does Not Mount
Confirmed
Solution: Haven't tested fix yet
E) Youtube app does not work
Confirmed
Solution: Confirmed
F) Orientation Sensor is not functional
Confirmed
Solution: "Rotating Screen" flips screen incorrectly so that capacitive buttons are on the top of the device
G) Honeycomb thinks Device Keyboard is enabled by default
Confirmed
Solution: Must be set on each boot
H) When pressing Quick Settings, an image that is semi transparent that is supposed to cover the entire screen isnt scaled properly
Confirmed
I) HQ Youtube does not work (LQ does on the mobile site)
Confirmed
J) Quick Settings Shortcut on Bottom Right Side (Wi-Fi Toggle, Brightness Slider, etc) appears for a second but disappears afterwards.
The widget that display battery level, time, etc stays active however no settings are located underneath it. While this menu is expanded a press on the bottom bar will cause the settings to briefly appear but then the whole menu will close
K) Flash Player is not Fully Functional
Not tested
"New" GSM bugs
1. Wi-fi settings are not saved on restart
2. Manage Applications and Running Services menu causes force close of settings
3. Small thing but Tab's first start had language set to Spanish (Not sure if it was spanish but it certainly was not English)
And as always 3G does not work (tried APN settings but it wouldn't let me save)
Alright I'm back to MIUI until I can find some more time on my hands
---------- Post added at 02:51 PM ---------- Previous post was at 02:31 PM ----------
If it were that simple I'm sure someone would have thought of that To be honest I think the problem is that the Tab is an extremely fractured device; it was really the first Android tablet to directly compete with the iPad, so it was spread as wide as possible. That's great for Samsung who got a pretty large base of customer but sucks for devs because the GSM and CDMA are 2 very different devices not to mention the P-1000N. When I got my Tab last month the first thing I noticed in this forum was the fragmentation between the different versions of Tabs. More profoundly this means that the developers are split apart, usually when one dev makes a break through everyone else can take advantage of it (i.e. the amazing Voodoo Sound/Color hacks) but not here. I feel like everyone is by themselves and I truly feel bad for the developers because they must make their own breakthroughs on top of dealing with complaints from Tab users with other versions that they want this awesome thing on their Tab. As if its no big deal to go and buy a $450 device to develop something as a hobby and then release it for free for people on the internet after already buying nearly the exact same device.
Sadly I think the Tab is a perfect storm working against modifying it in any ground breaking ways. Don't get me wrong I love my Tab and will try to help getting Honeycomb running but I almost feel like it would just be easier to wait for Ice Cream Sandwhich. /rant
Click to expand...
Click to collapse
Wow now that is the kinda posts i like seeing on here! I will try to update the OP tonight with this info! Thanks so much! Definitely echo your sentiments about the fractured and fragmented development we have going on here, it really sucks =/
Ive found out that replacing the existing Gallery with Gallery3D should fix the FC that keeps popping up.
I think Ive found a working Youtube App (in LQ).
Ive also found a hint towards solving the sdcard mounting issue. Its not the vold.fstab its something either in the framework or ramdisk within the kernel, according to the Nook Color Forums.
This thread is interesting: http://forum.xda-developers.com/showthread.php?t=1062626 , actually the entire nook color forum is interesting for finding fixes.
Also changing the dalvik_heapsize to a certain value is supposed to increase app compatibility. Before I update the OP with some of these things, I wanna do a little more testing and see what I can come up with.
Sorry to bother for help,
Sorry to bother you guys for help, but I've been trying to install Oldmacnut's updated of Spacemoose's CDMA Honeycomb (2.5.1) for hours now, with no success.
I used Rodderick's awesome stock rom/kernel and got into clockworkmod (using 4.0.1.5 or 3.0.0.0), installed the zip from there, then rebooted the phone, but I would either 1) be stuck at logo for 10+ minutes 2) see the Sprint startup video loop over and over again, or 3) get stuck on a turned on, but black screen.
How did you guys install Honeycomb on your CDMA tab? Am I doing something wrong? Should I use Spacemoose's 2.5 rom instead of Oldmacnut's?
EDIT: NEVER MIND, IT BOOTED INTO HONEYCOMB. I am in a foreign language, haha, I'm guessing Portuguese?
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
iliveinabucket said:
EDIT EDIT: Google Translate detects the language as Catalan. Haha!
Click to expand...
Click to collapse
Hehe that happened to me as well
First Impressions and problems encountered
HOLY SHOOT THIS IS QUITE FAST!
Considering there is no graphics acceleration support, Honeycomb runs much faster than I anticipated. SD card support is fantastic, and so is hearing sound! (I love you OMC) The UI is awetastic and the standard web browser is blazing fast. Scrolling in web pages is faster on Honeycomb than on Gingerbread stock.
The jittery touch screen bug I have is still there, unfortunately. Damn bug drives me crazy sometimes. I'm sure somebody has this problem that many of us have but have not found a fix to: http://forum.xda-developers.com/showthread.php?t=970965
Basically, when I hold down my finger to scroll on white or light-color backgrounds, the screen shakes back and forth in a spastic, noticeable way, especially when I hold it in place. This happens on every single rom I've been on, froyo, GB, CM7, and now Honeycomb. Has anyone found a fix for that yet?
Anyways, I think all the known Honeycomb bugs are true to me too. Youtube force closes on me, GPS doesn't work, auto-orientation doesn't work. Strangely enough, Quick Settings doesn't work for me. Anyone encounter that?
Wow. It's been a long time since I made anything useful. Not being able to use NFC with the screen off has always been a pet peeve of mine with my Nexus, so I figured I'd fix it
This is a modified Nfc.apk, which is the system NFC service that runs at boot. It allows you to scan NFC tags either with the screen totally off, or with the screen on but still at the lockscreen. You get to choose which one you want to flash. Just download one of the zips below, and flash it via recovery (tested with ClockworkMod). To restore to stock, just pick the stock version.
The screen off version means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
This has been compiled against CyanogenMod and tested on my own self-built tree based off CyanogenMod source. There is nothing here that should be specific to that ROM.
Devices
Sprint Galaxy Nexus (toroplus)
Fully working on CyanogenMod based ROMs
Fully functional on most AOKP ROMs. Throws random errors on some, but everything still works.
Not functional on some stock ROMs
GSM Galaxy Nexus (maguro)
Fully working on CyanogenMod based ROMs
Fully functional on most AOKP ROMs. Throws random errors on some, but everything still works.
Not functional on some stock ROMs
Verizon Galaxy Nexus (toro)
Untested as far as I know. If you test it let me know
Should be similar to other Galaxy Nexus SKUs
HTC One X
The user StephanSch has created a version for the One X. Get it in this post.
Only screen off seems to work, not lockscreen.
Don't know if this is for the Qualcomm S4 based One X or the Tegra 3 base. Not sure about carrier versions either.
Samsung Galaxy SIII
The user mayhemer has created a version for the SIII. Get it in this post.
I'm not aware of which version of the SIII this is for, now which ROM. As soon as I have info, I'll update it here.
Nexus S
Reported working from at least one user. Don't know GSM or CDMA version, nor which ROM.
Probably working on any CM9 build for either SKU, and possibly stock or AOKP.
It probably will not work on any manufacturer based skins on any other device.
If you try it on any other device, please let me know how it goes! I'll update the OP with your results!
Also of note, I do not know if this will allow you to use Wallet any differently than you can right now. I don't have any way to test it, and don't personally use Wallet. If you do, let me know whether it works or not so I can update this post!
Liability Disclaimer: As always, I hereby absolve myself of responsibility for any damage you cause to your phone by flashing this. There is inherent risk in modding your device, and by flashing anything in this thread you are taking that risk into your own hands. If something goes wrong, I will try and help, but I am not God.
Source Code Disclaimer: The only code modified here was given under the Apache v2 license. That means that I am not required to release source for this. It is an incredibly simple mod at this point, but I plan on taking it into the next level and creating a patch that makes this an option in settings, rather than a zip you have to flash. I will release source with this, but I want to wait until I clean it up and submit it to the CyanogenMod Gerrit as a full feature, rather than a cheap hack! Sorry if that disappoints anyone, I just wanted to get this out ASAP.
In the meantime, I explain what I'm doing in this post. That should be enough info if you're compiling from source, and might be enough if you are using a Smali edit. If you're critically concerned about it, shoot me a PM or an email and I'll try and help more.
How things stand for Jellybean:
I put this on hold for a while. The further I got into making this a toggleable option in settings, the deeper things ran into the system code. With the big change to Jellybean around the corner, I want to wait until Jellybean becomes the main CM branch so I can avoid the breaks that all the code churn will cause. I'm not done with this, but there's no point in putting the work in to make it fully functional when CM10 is around the corner to break it all. I'll get on it as soon as CM10 becomes closer to release. Before the code freeze for CM10.
In the mean time, @PHtQuE got ahold of me on Twitter and I told him what was happening. I gave him a couple pointers and he got it compiling on Jellybean at the same level it is right now on ICS. I may be wrong, but I believe this is his post right here. Regardless, this is a working screenoff version for JB.
Reserved, just in case...
That will definetly come in good use. Thanks
Sent From My Old Epic 4g via XDA Premium
This is nice! Thanks! One thing that I thought would be useful is to have a notification pull down toggle for NFC. so you think that's possible?
Sent from my Galaxy Nexus using XDA
This is handy thanks dog lol.
Sent from my Galaxy Nexus
Hmmm... I've always been able to use Google wallet with the screen off. I'm not sure about any other nfc use though.
Awesome man, thanks. Just bought some NFC stickers to mess around with and this was my biggest problem. Really appreciate it.
Nice!! So the screen of one is only if the screen is off without a lockscreen?
davidrules7778 said:
Nice!! So the screen of one is only if the screen is off without a lockscreen?
Click to expand...
Click to collapse
No. Sorry, I'll update the OP to be a little more clear.
Screen off means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
pastert33 said:
This is nice! Thanks! One thing that I thought would be useful is to have a notification pull down toggle for NFC. so you think that's possible?
Click to expand...
Click to collapse
It's definitely possible. I'm working on getting the option in Settings now, and should have it working by the end of the day. Once there's an option in Settings, it should be super simple to add a notification bar toggle option as well. Haven't messed with that part before, but it's not too dissimilar from WiFi toggling, so I've got code to look at.
I was hoping to get the settings mod done in time to submit it to CM before they started the code freeze for CM9. Well, they went into code freeze this morning so I missed that. I'll still get it submitted ASAP, but don't expect to see it in the initial CM9 official build unless you use the nightlies. I'll of course update everything once I submit the patch and if it gets accepted.
Geniusdog254 said:
No. Sorry, I'll update the OP to be a little more clear.
Screen off means you can ALWAYS scan an NFC tag. Don't have to turn the screen on or anything. Just touch the phone to the tag.
The lockscreen version lets you scan a tag whenever the screen is on, but it doesn't have to be unlocked. You can't scan while the screen is off, but you can just touch the power button to get to the lockscreen and then scan. If you have a passcode, no need to unlock your phone to scan a tag.
It's definitely possible. I'm working on getting the option in Settings now, and should have it working by the end of the day. Once there's an option in Settings, it should be super simple to add a notification bar toggle option as well. Haven't messed with that part before, but it's not too dissimilar from WiFi toggling, so I've got code to look at.
I was hoping to get the settings mod done in time to submit it to CM before they started the code freeze for CM9. Well, they went into code freeze this morning so I missed that. I'll still get it submitted ASAP, but don't expect to see it in the initial CM9 official build unless you use the nightlies. I'll of course update everything once I submit the patch and if it gets accepted.
Click to expand...
Click to collapse
Darn it LOL i would love to have one that works with both
Great work tho, i will probaly get the lockscreen one
Any thoughts as to if this will work on the One X? I'm backing up my stock NFC.apk anyhow and am going to test it, but I thought I'd ask in advance.
agentdr8 said:
Any thoughts as to if this will work on the One X? I'm backing up my stock NFC.apk anyhow and am going to test it, but I thought I'd ask in advance.
Click to expand...
Click to collapse
In theory, it should work on any 4.0.4 base ROM, on any NFC device. No guarantees though
This is just what I've been looking for (FOR AGES) I know that it doesn't come like this from stock, due to the potential security risks, but sod it! Lol, i love it.
Thanks for the fantastic work
Rumble
Sent from my Galaxy Nexus using xda premium
im curious as to the effect on battery life. how noticeable is the difference?
I think that this is a great feature. But I thought that the reason
the NFC only worked with the screen on and phone unlocked was
a security reason. Meaning someone could not just walk up to
you and scan your phone without you knowing. you would have to
have the phone on for anything to work. I think that the settings
idea is great that way if you want to open then you can have it open
if you want it closed then you can keep it like stock. Great work. Worked
good on my GNexus (Sprint).
zcmack said:
im curious as to the effect on battery life. how noticeable is the difference?
Click to expand...
Click to collapse
I can't speak for the battery life, as my phone is plugged in either for tethering or testing code all day. Shouldn't be too noticeable.
Smurph82 said:
I think that this is a great feature. But I thought that the reason
the NFC only worked with the screen on and phone unlocked was
a security reason. Meaning someone could not just walk up to
you and scan your phone without you knowing. you would have to
have the phone on for anything to work. I think that the settings
idea is great that way if you want to open then you can have it open
if you want it closed then you can keep it like stock. Great work. Worked
good on my GNexus (Sprint).
Click to expand...
Click to collapse
Security is exactly the reason it doesn't come like this by default. It's also why I made two versions. If you're worried about security, then flash the lockscreen version and you have to turn the phone on to be able to scan.
Currently, there is no way that I know of to get anything malicious by scanning against someone's will. It doesn't just offer up credit card numbers when you scan it. If you have NFC Task manager on your phone, someone could scan it and make it start an app you have installed or turn off wifi or something mundane like that, but that's about it. Plus they'd have to get within ~5" of your pocket
Geniusdog254 said:
In theory, it should work on any 4.0.4 base ROM, on any NFC device. No guarantees though
Click to expand...
Click to collapse
It would appear that the One X's Nfc.apk has different hardware support. When I flashed your zip, NFC ReTag couldn't detect NFC hardware any more. And the option for NFC disappeared in Settings. Nothing a restore of the original apk couldn't fix, but it's unfortunate it didn't work.
Any chance you'd be willing to share what edits you made? If it's smali, I can probably tweak the One X's apk to be similar.
agentdr8 said:
It would appear that the One X's Nfc.apk has different hardware support. When I flashed your zip, NFC ReTag couldn't detect NFC hardware any more. And the option for NFC disappeared in Settings. Nothing a restore of the original apk couldn't fix, but it's unfortunate it didn't work.
Any chance you'd be willing to share what edits you made? If it's smali, I can probably tweak the One X's apk to be similar.
Click to expand...
Click to collapse
It's actually compiled from source. I've never messed with Smali, so I don't know how useful this will be. The easiest way is to tweak a variable called POLLING_MODE in the NfcService class. There are a couple different settings. 3 is the default, 2 works on lockscreen or unlocked, and 1 works with the screen off, at the lockscreen, or unlocked.
I don't think Smali keeps variable or function names, so that might be of no use at all.. The other method, in a function called applyRouting() there are a couple if/else statements that check if the current state matches POLLING_MODE or not. If you take those out, then it should also work although for some reason that only seems to enable it to the lockscreen level.
You should be able to see a copy of the file here, if that helps.
Geniusdog254 said:
Security is exactly the reason it doesn't come like this by default. It's also why I made two versions. If you're worried about security, then flash the lockscreen version and you have to turn the phone on to be able to scan.
Currently, there is no way that I know of to get anything malicious by scanning against someone's will. It doesn't just offer up credit card numbers when you scan it. If you have NFC Task manager on your phone, someone could scan it and make it start an app you have installed or turn off wifi or something mundane like that, but that's about it. Plus they'd have to get within ~5" of your pocket
Click to expand...
Click to collapse
I did not mean anything by my comment, I think that having to turn the phone
on to use it is a bit much. I like that you have the ability to run it form the lock
screen. I understand that right now you really cannot do much with the NFC,
hacker wise, other than changing settings you are not stealing information by
scanning. But being that NFC is still new(ish) I also feel that all the security
holes have not been discovered. I just wanted people to consider every angle.
I still think that you have created a great feature.
I love what I'm seeing here, well done! Can anyone confirm if this breaks Google Wallet functionality?
Released to market!
Remember all those nifty little tricks in Sense which you sometimes miss on cm7 and cm9? I thought about getting those features into an app which can be used with all ROMS. The main one I'm thinking of is the flip for speaker but there are also other ones like the loud ring in pocket and so on. It was really something that I wanted in an app. The closest one I found was Sanity which switched on the speaker as soon as the user takes the phone off his ear, which can lead to troubles such as in a classroom/meeting.
So far, I have a working version of the Flip For Speaker with an option to disable it of course. I'll will try to port the other features. I would like to get your opinion of small features that improve the usability like this one and I can try including them as well. They can be from other ROMS of other phones like say something from TouchWiz or MotoBlur. Post them here and I'll see what I can do.
Meanwhile, here is an alpha version of the app if you would like to test it out. If you run into errors, let me know. Try getting a logcat if you can. I'm open to suggestions.
Current Features:
Flip to Silence
Flip for Speaker
Pick up to answer (Meaning hold it up to your ear)
Changelog:
Version 1.0
Initial market release!
Get it from: https://play.google.com/store/apps/details?id=com.ajaykumar.sense
Version 0.6
Fixed the mute bug on pick up to answer
Version 0.5.1
Holo theme for ICS onwards
Version 0.5
Options for speaker volume and headset volume
Version 0.4
Pick up to answer
Version 0.3
+Should support other devices (Earlier had some issues with the sensor readings)
^Improved the usage of proximity sensor
Version 0.2
+Added option for flip to silence call
Version 0.1.1a
^Fixed bugs
Version 0.1a
+Flip to silence call
^Improved flip mechanism by including pitch and roll.
Version 0
+Flip for speaker
I would also like a nice name for the app so suggestions are welcome!(Don't want to use the word sense in case of any copyright issues later on when hopefully, I can release the app into the Market).
If anyone is willing to test on other devices, please let me know.
Source code: https://github.com/ajaykumarkannan/Sense-and-Sanity
You can report issues and see the existing issues here: https://github.com/ajaykumarkannan/Sense-and-Sanity/issues?state=open
You can also make feature requests there.
Heres a good app to control flip to speaker: https://play.google.com/store/apps/details?id=com.matthew.rice
Only thing is, its a paid app, but works very well for me.
Nice find!
I think I'll continue developing this app so that it can suit my purposes better and it's fun developing
I'm also thinking of adding flip to silence feature. Anything else you would like to see, let me know.
Can you develop apps like internet pass through of sense ?
Sent from my Wildfire S A510e using Tapatalk 2
AceRoom said:
Remember all those nifty little tricks in Sense which you sometimes miss on cm7 and cm9? I thought about getting those features into an app which can be used with all ROMS. The main one I'm thinking of is the flip for speaker but there are also other ones like the loud ring in pocket and so on. It was really something that I wanted in an app. The closest one I found was Sanity which switched on the speaker as soon as the user takes the phone off his ear, which can lead to troubles such as in a classroom/meeting.
So far, I have a working version of the Flip For Speaker with an option to disable it of course. I'll will try to port the other features. I would like to get your opinion of small features that improve the usability like this one and I can try including them as well. They can be from other ROMS of other phones like say something from TouchWiz or MotoBlur. Post them here and I'll see what I can do.
Meanwhile, here is an alpha version of the app if you would like to test it out. If you run into errors, let me know. Try getting a logcat if you can. I'm open to suggestions.
Also, I would like a nice name for the app (Don't want to use the word sense in case of any copyright issues later on when hopefully, I can release the app into the Market).
--------------------------
Mods, could you please move this thread to the app section. I accidentally posted in general.
Click to expand...
Click to collapse
What about the clock with the same animation features?? Would love to have it
Sent from my X10i using xda premium
idhbar said:
Can you develop apps like internet pass through of sense ?
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
You can use connectify for that
Sent from my Wild(sexy)fire S
Had a bug in the earlier version I posted. I thought that only pitch would be enough so the speaker kept turning on at incorrect moments. I've fixed that I'll post an update tonight.
As for the sense clock, sorry. I'm not that good at theming nor do I have enough patience for something like that! Henry would be a better person to ask. You can also check out UCCW clock widget which has sense clock like themes.
For internet passthrough, you can checkout this thing called "Reverse Tethering". I haven't used it personally but it should work.
Fixed the issue with the roll and also added flip for silence working. Updated apk in the OP. I've tested it very briefly cause I'm about to head off to sleep. Let me know if you find some issues.
Updated with a few bug fixes and hopefully should now support other devices because I've changed the API now. Check the changelog.
Added Pick up to Answer. Updated OP.
'senseable speaker control'
or
'non-sense speaker control'
Just a couple of things that popped in my head
Is this still in development? I really liked this idea and would pay a full app to do the "nifity tricks" (my suggested app name )
Sent from my HTC Sensation using xda premium
Yes, of course. I have a pretty major exam tomorrow so after that I would be getting back to development. Any features in particular you would like to see?
Sent from my BlackBerry Runtime for Android Apps using Tapatalk 2
AceRoom said:
Yes, of course. I have a pretty major exam tomorrow so after that I would be getting back to development. Any features in particular you would like to see?
Sent from my BlackBerry Runtime for Android Apps using Tapatalk 2
Click to expand...
Click to collapse
Hey AceRoom, great work on the sense app hey. Features I know I definitely miss on CM7 and CM9 roms are the jus the three you mentioned earlier on - quiet ring on pickup - flip for speaker and pocket mode. The rest are not so important but if you could get those working on any cm7 or CM9 rom - that would totally rock!
Looking forward to more of your work
Cheers
thanks a lot, i was searching all over for these features.
---------- Post added at 05:28 PM ---------- Previous post was at 05:24 PM ----------
since this is an application, why dont you add it to the play store?
Amazing! I think it works better than the actual sense version
manoruz said:
Hey AceRoom, great work on the sense app hey. Features I know I definitely miss on CM7 and CM9 roms are the jus the three you mentioned earlier on - quiet ring on pickup - flip for speaker and pocket mode. The rest are not so important but if you could get those working on any cm7 or CM9 rom - that would totally rock!
Looking forward to more of your work
Cheers
Click to expand...
Click to collapse
I think those two features are already working well from the few guys I gave it to. They were mostly running stock ROMs (Samsung and LG phones).
MidhunCN said:
since this is an application, why dont you add it to the play store?
Click to expand...
Click to collapse
I thought I'll do that once I confirm that the basic features are working on all the devices I have access to.
vbhtt said:
Amazing! I think it works better than the actual sense version
Click to expand...
Click to collapse
Thanks! Appreciate that!
I'm noticing some bugs with the pickup to answer. Is it working completely well for anyone?
This app makes me feel like a Jedi, just sayin'.
-----------
"You can overclock as much as you want, your phone will always seem too slow."
AceRoom said:
I'm noticing some bugs with the pickup to answer. Is it working completely well for anyone?
Click to expand...
Click to collapse
Actually, no. It picks up fine but the caller can't hear me. So I've just turned it off till you you fix it.
For some reason, it mutes the phone when it does that. So I tried explicity unmuting the phone and it still doesn't work. You can unmute it manually but it kind of defeats the purpose anyhow!
It's actually a hack I found somewhere since Android stopped supporting the call answer API after 2.3 (But had it in 2.2 and earlier).
The next thing I'm planning on adding is a speaker volume and normal volume (Because I find that I have to increase the volume when I flip for speaker usually).
I've tested it on the WFS only on CM9. What ROMs are the rest of you guys using?
Are there any known 4.3 or 4.4 ROMs with working phone mic?
I've used CM 10.2 Stable (4.3) and Carbon Rom (4.4.2). Both work great, the only issue is that the headset is not usable for calls (low mic output). My solution for now is using the earbud/mic, but I'm curious to know if anyone has made progress on this. Aside from this, the various ROMs are near perfect for my needs.
I'm not very knowledgeable on the details of writing ROMs, but would any type of source code release from LG help developers solve this? Curious to know what the main hurdles are for the devs and what tools they need.
Thanks.
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Neroga said:
Wish I could tell ya but I don't have a headset with a mic. I'd say give AICP a try since it uses AOKP sources instead of CM. Might give ya a better outcome.
Sent from my AICP 4.4 LG-E980
Click to expand...
Click to collapse
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
markusrussell225 said:
Thanks for the suggestion, downloading now.
Do phone calls work fine on yours?
Click to expand...
Click to collapse
Still no luck on a solid working phone microphone (low volume on other end). And the search continues.
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
markusrussell225 said:
Now that mid March has come around, has anyone had any good luck with a working in call microphone?
I was previously using several 4.4.2 Builds however, the need for a working phone mic was too critical for daily usage.
I'm using a 4.3 build (Slim Bean) which I believe is the only one with a working phone. The build is an unofficial beta and the only real issues are lack of microSD function, FC on Google Drive, and a few freezes here and there. Overall it's usable for my needs but would like to get back onto 4.4.2 granted the phone mic works.
Any suggestions/advice would be great. Thanks!
Click to expand...
Click to collapse
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
ja.andro said:
I don't know much, plus i am still on stock but i will suggest you to ask your query and issues on particular custom ROM posts. i have seen people getting response faster and if in case there is a bug, high chances that developer of that particular ROM can fix it :thumbup:
Sent from my LG-E988 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ask because this is a problem has existed on all known roms since 4.3.1 for the E980 on ATT. Never been able to get a straight answer anywhere so I figure I would generically post it. I have reached out to some devs but not luck.
Any success on your searching?
thureos said:
Any success on your searching?
Click to expand...
Click to collapse
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
markusrussell225 said:
---
Here is a manual fix for the in call mic from JustinNL on XDA:
Step 1:
download a "build.prop editor app", I used: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Step 2:
Modify these 2 specs in the build prop editor
persist.audio.handset.mic.type=digital --> replace digital with analog
persist.audio.dualmic.config=endfire -- replace endfire with false
Since i changed it i haven't had any complaints so far but flashing to new nightly makes it revert again, keep that in mind."
Been working great for myself and others.
Click to expand...
Click to collapse
I saw that solution but I went back to rooted and debloated stock, I am very pleased with speed and stability.
Thanks
i've made the edits suggested on that post and still get the same issue...i dont remember having this issue before but i thnk youre right and the previous roms werent 4.4...oh well i live on the phone for work so back to stock for me. for now i guess...wanting a new phone anyways, hope we get the g pro 2 or g3 soon
So I have been in this modding android game for quite some time since I had an LG G3 and then I moved over to the Nexus 6 for about 2 years and some of these custom roms are just awesome but one thing I cannot get rid of properly are the inbuilt AOSP apps..
on the Nexus 6 a few years back somebody made a flashable zip that got rid of all of them and the boot animation but then fixed the boot animation being deleted and unfortunately time to change technology has changed and that doesn't work on this phone obviously.
I have tried using the magisk debloater and it just a little too complicated for me because I don't like having two of the same apps one being Google the other being AOSP and any other gaps package I flash besides the razorlove gapps fail when flashing a custom ROM..
I've tried using opengapps and I thought when flashing that package the AOSP apps get replaced with the Google version of them.
Would anybody mind listing what AOSP apps I can remove completely and I apologize if it's already on the thread but I didn't really see anything or maybe I just wasn't looking in the right place but can you guys help me out? I really like the RR ROM but the AOSP apps just bothered the hell out of me. I've tried using titanium to completely remove some of them like the AOSP Keyboard but it doesn't fully remove them and I don't want to go into the files that I don't know about and screw up my phone..
So right now I'm on stock and the limitations kind of suck so if anybody could you know help me out listing a method that they use to get rid of them that actually works or listing the ones that I can remove and what program I can use to remove them I do not want to disable them I want to remove them... Or because I know how to use Linux and what not you know maybe somebody could show me how to make a flashable zip that will remove them and I will gladly share it to the community but I'm looking for anything that helps.
It would be greatly appreciated!
soateufel said:
So I have been in this modding android game for quite some time since I had an LG G3 and then I moved over to the Nexus 6 for about 2 years and some of these custom roms are just awesome but one thing I cannot get rid of properly are the inbuilt AOSP apps..
on the Nexus 6 a few years back somebody made a flashable zip that got rid of all of them and the boot animation but then fixed the boot animation being deleted and unfortunately time to change technology has changed and that doesn't work on this phone obviously.
I have tried using the magisk debloater and it just a little too complicated for me because I don't like having two of the same apps one being Google the other being AOSP and any other gaps package I flash besides the razorlove gapps fail when flashing a custom ROM..
I've tried using opengapps and I thought when flashing that package the AOSP apps get replaced with the Google version of them.
Would anybody mind listing what AOSP apps I can remove completely and I apologize if it's already on the thread but I didn't really see anything or maybe I just wasn't looking in the right place but can you guys help me out? I really like the RR ROM but the AOSP apps just bothered the hell out of me. I've tried using titanium to completely remove some of them like the AOSP Keyboard but it doesn't fully remove them and I don't want to go into the files that I don't know about and screw up my phone..
So right now I'm on stock and the limitations kind of suck so if anybody could you know help me out listing a method that they use to get rid of them that actually works or listing the ones that I can remove and what program I can use to remove them I do not want to disable them I want to remove them... Or because I know how to use Linux and what not you know maybe somebody could show me how to make a flashable zip that will remove them and I will gladly share it to the community but I'm looking for anything that helps.
It would be greatly appreciated!
Click to expand...
Click to collapse
You do realize that AOSP is not a single project like some rom developers, right? If someone publishes an "AOSP" rom, that doesn't mean that they are following some kind of standards or rules.
nabbed said:
You do realize that AOSP is not a single project like some rom developers, right? If someone publishes an "AOSP" rom, that doesn't mean that they are following some kind of standards or rules.
Click to expand...
Click to collapse
Well obviously but what I'm saying is pretty much every ROM that I flash seems to have the built-in apps that are AOSP based or maybe I'm not saying it right but basically every ROM that I've tried (dirty unicorns, Resurrection Remix, carbon, dotOS, sudomod,) all have built-in AOSP Keyboard AOSP phone AOSP calendar AOSP email **** like that and that's what I want to remove
soateufel said:
Well obviously but what I'm saying is pretty much every ROM that I flash seems to have the built-in apps that are AOSP based or maybe I'm not saying it right but basically every ROM that I've tried (dirty unicorns, Resurrection Remix, carbon, dotOS, sudomod,) all have built-in AOSP Keyboard AOSP phone AOSP calendar AOSP email **** like that and that's what I want to remove
Click to expand...
Click to collapse
But I am doing some research on a flashable zip creator from XDA and hopefully I can make some progress with it
soateufel said:
Well obviously but what I'm saying is pretty much every ROM that I flash seems to have the built-in apps that are AOSP based or maybe I'm not saying it right but basically every ROM that I've tried (dirty unicorns, Resurrection Remix, carbon, dotOS, sudomod,) all have built-in AOSP Keyboard AOSP phone AOSP calendar AOSP email **** like that and that's what I want to remove
Click to expand...
Click to collapse
A piece of advice. Get rid of your Pixel as soon as you can. It's a bug testing platform for Google. Samsung, HTC, LG, Oneplus take buggy Google code and refine it. Google doesn't bother.
I only keep this $960 piece of **** (which is now worth less that $300) because I have no other alternative at the moment. As soon as I can dump it for a real a phone, I will.
I'm good thanks I do my research before I buy my phones and I will never buy another Samsung again and dumping my phone is not an option right now if it was I get me the Rog phone from Asus that thing is a beast
soateufel said:
I'm good thanks I do my research before I buy my phones and I will never buy another Samsung again and dumping my phone is not an option right now if it was I get me the Rog phone from Asus that thing is a beast
Click to expand...
Click to collapse
I used an S9 for a little while when I was setting it up for a friend. It's a marvelous phone. I have owned multiple HTC flagships in the past, and they were stellar. I have heard that LG and Oneplus were excellent. My last phone before Pixel XL was Note 7, which was absolutely amazing, one of a kind. This pos Pixel XL has been nothing but bug ridden nightmare. The only reason why I keep it around is because of Project FI. It's because it's cheap. Goddamn $960 nightmare on top of that.
Also, please use punctuation next time. Not using it seems like an insult, but maybe that's just me.
I like my pixel XL. No bugs here.
nabbed said:
I used an S9 for a little while when I was setting it up for a friend. It's a marvelous phone. I have owned multiple HTC flagships in the past, and they were stellar. I have heard that LG and Oneplus were excellent. My last phone before Pixel XL was Note 7, which was absolutely amazing, one of a kind. This pos Pixel XL has been nothing but bug ridden nightmare. The only reason why I keep it around is because of Project FI. It's because it's cheap. Goddamn $960 nightmare on top of that.
Also, please use punctuation next time. Not using it seems like an insult, but maybe that's just me.
Click to expand...
Click to collapse
lafester said:
I like my pixel XL. No bugs here.
Click to expand...
Click to collapse
Ignorance is bliss.
nabbed said:
Ignorance is bliss.
Click to expand...
Click to collapse
Maybe you can fill us in on all these bugs you speak of. Would hate to continue to be ignorant.
nabbed said:
Ignorance is bliss.
Click to expand...
Click to collapse
lafester said:
Maybe you can fill us in on all these bugs you speak of. Would hate to continue to be ignorant.
Click to expand...
Click to collapse
I'd like to know too, cause I must be missing something. I have absolutely no issues with my device...
lafester said:
Maybe you can fill us in on all these bugs you speak of. Would hate to continue to be ignorant.
Click to expand...
Click to collapse
Click on my profile and find new threads started by me in this subforum.
I believe every single new thread was me complaining about one bug or another.
The biggest one that is always on my mind though, and which is almost a deal breaker, was introduced by Google in the 7.0.2 update. And they still haven't fixed it, but all other manufacturers have - I know for a fact that this bug was fixed in Oreo by Samsung and Oneplus.
It's where you wear a smartwatch which can make and receive phone calls, such as my beautiful Huawei Watch with a gorgeous custom band, and then you get inside your car with a bluetooth hands-free car kit, or just a bluetooth headset, which then improperly connects to the phone as "Connected (no phone)." So you cannot use it. If you don't wear a watch, then everything works fine with a kit or bt headset. This is the reason why I don't wear my beautiful watch anymore. Google needs to fire their bluetooth stack programmer.
nabbed said:
I used an S9 for a little while when I was setting it up for a friend. It's a marvelous phone. I have owned multiple HTC flagships in the past, and they were stellar. I have heard that LG and Oneplus were excellent. My last phone before Pixel XL was Note 7, which was absolutely amazing, one of a kind. This pos Pixel XL has been nothing but bug ridden nightmare. The only reason why I keep it around is because of Project FI. It's because it's cheap. Goddamn $960 nightmare on top of that.
Also, please use punctuation next time. Not using it seems like an insult, but maybe that's just me.
Click to expand...
Click to collapse
My bad. I use speech to text a lot and I don't like using punctuation when speaking. It causes some bad habits.
Update though, upon doing further research making a flashable zip is complicated but I should have it all figured out by the end of the week and I'm not really having any bugs with the AOSP apps I just don't like looking in my app drawer and seeing there's duplicates and I really don't want to manually hide all of them each time I flash a ROM or something and do a backup.
On a side note I just found a Chrome extension that allows speech to text and is very good with no ads. If you're like me and you use your voice more than you use your keyboard, look up voice in voice typing under Chrome extensions pretty damn simple.
soateufel said:
My bad. I use speech to text a lot and I don't like using punctuation when speaking. It causes some bad habits.
Update though, upon doing further research making a flashable zip is complicated but I should have it all figured out by the end of the week and I'm not really having any bugs with the AOSP apps I just don't like looking in my app drawer and seeing there's duplicates and I really don't want to manually hide all of them each time I flash a ROM or something and do a backup.
On a side note I just found a Chrome extension that allows speech to text and is very good with no ads. If you're like me and you use your voice more than you use your keyboard, look up voice in voice typing under Chrome extensions pretty damn simple.
Click to expand...
Click to collapse
Sorry for hijacking your thread -was not my intention.
Making a flashable zip is easy with the tool I link in this thread. https://forum.xda-developers.com/pixel-xl/how-to/noob-friendly-tips-tricks-information-t3798529
soateufel said:
Update though, upon doing further research making a flashable zip is complicated but I should have it all figured out by the end of the week and I'm not really having any bugs with the AOSP apps I just don't like looking in my app drawer and seeing there's duplicates and I really don't want to manually hide all of them each time I flash a ROM or something and do a backup.
Click to expand...
Click to collapse
A friend of mine made a script specifically for what you are trying to do, granted, it's for a different device and older version of Android. Some small modification should be all it needs to suit your purpose, if nothing else, it may contain some useful information.
The thread is located here (Keep in mind, he's from Brazil, so his English is a little rough =)
nabbed said:
Sorry for hijacking your thread -was not my intention.
Click to expand...
Click to collapse
You are completely fine. I'm shocked how nice people are on here LOL usually people are just mean and think they have the right answer and I have to accept it no matter what and I just don't like people who are so full of themselves so thank you.
I've been trying to research this but I was supposed to have surgery today and I was getting ready for that and unfortunately it was cancelled without my knowledge so that was pretty stressful and now I have to start the whole process over again because the doctors I was going to go to no longer accept my insurance and nobody told me so I'm still going to work on this it's just going to be a little bit of a process.
soateufel said:
You are completely fine. I'm shocked how nice people are on here LOL usually people are just mean and think they have the right answer and I have to accept it no matter what and I just don't like people who are so full of themselves so thank you.
I've been trying to research this but I was supposed to have surgery today and I was getting ready for that and unfortunately it was cancelled without my knowledge so that was pretty stressful and now I have to start the whole process over again because the doctors I was going to go to no longer accept my insurance and nobody told me so I'm still going to work on this it's just going to be a little bit of a process.
Click to expand...
Click to collapse
As a side note, I am now in the same boat as you. I have a Oneplus 6 now, silk white, which is gorgeous. But it has double apps like yours - 2 calendars, 2 calculators, 2 message apps, 2 clock apps etc. I don't even really know which ones are Google and which ones are Oneplus - I think the round icons are Google, but rectangular icons are Oneplus. Plus I don't know which apps are better. I think that I will use some of them for a while and disable the least appealing ones.
There are only a handful, and maybe that's what you can do? Just disable? If you cannot disable from the main Android interface, you can do it from adb. There are commands that can disable and enable app packages from adb.
Hey guys I'm sorry it's been awhile since I've kept up with you guys. So a little side note
I have started this project it is my very first project on my GitHub.
But my problem is I have no idea how to even start this I mean I tried using the flashable zip creator and it pulled the system apps but I'm at a loss here any help would be greatly appreciated..
You can view the project at this link by the way
https://github.com/arkhamsaiyan/Marlin-AOSP-app-remover