yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] fifthelement:
Here is another logcat. I guess problem is related to this line :

Adreno200-EGL: <qeglDrvAPI_eglGetConfigAttrib:491>: EGL_BAD_ATTRIBUTE

or may be these lines :

07-12 00:18:07.044 6543 6561 E Adreno200-EGLSUB: <ShadowBufferCreate:597>: alloc mmap(fd=39, size=8355840, prot=3) failed (Try again)
07-12 00:18:07.044 6543 6561 E Adreno200-EGLSUB: <ShadowWindowDequeueBuffer:763>: <failed to deque a buffer>
07-12 00:18:07.044 6543 6561 W Adreno200-EGLSUB: <GetBackBuffer:2382>: global_shadow_buffer is NULL
07-12 00:18:07.044 6543 6561 W Adreno200-ES20: <gl2_surface_swap:43>: GL_OUT_OF_MEMORY
07-12 00:18:07.044 6543 6561 W Adreno200-EGL: <qeglDrvAPI_eglSwapBuffers:3498>: EGL_BAD_ALLOC
07-12 00:18:07.044 6543 6561 W GLThread: eglSwapBuffers failed: EGL_BAD_ALLOC
[One (M7) Original Android Development] spaboleo:
To be honest, there are only two touch-"hardware"-buttons. fullstop.

The Logo button can't count as you would have to touch the very upper part of the Logo. It is just to flimsey to work realiably (reason #1) and this is only one of the reasons why I decided to go back to the software navbar.

Yes, I am sacrificing screen estate with it, but it doesn't really matter, as at a density of 361dpi with this high resolution of over 2 million pixels (!) there is enough content to be displayed. This was different on all my previous devices...even on the Galaxy Nexus (0,92MP) or Nexus 4 (0,98MP).

Furthermore two buttons are not enough.

It can't even handle the basic functionality, which are back / home / search / recents, properly, which means without combining functions in a weird manner.

(Note that the double tap to recents function is not available on most AOSP custom roms.)

What if you got used to many more of the AOSP features such as "long-press back to kill" or "long-press recents to jump to the last used app"? (reason #2)

And what if you want to use the wake and sleep methods in addition?

And third the menu button issue. (reason #3)

Not every app is fully following the new holo UI design guidelines and has the 3-dot-menu button built into their design. There are still a lot of apps where some functions are "hidden" in the contextmenus. This was the only reason to implement the "action overflow" for the menu button in the first place.

On devices without hardware buttons this is solved (quite elegantly) by the optional 3-dot-button on the right side of the navbar. When ever there is a menu, but no dedicated 3-dot-menu button is incorporated in the app's layout it appears.

Binding it natively to, let's say the "HTC Logo button", as many of the xda users seem to do, is not a sufficient solution, as there is no indication whatsoever if there is a context-menu. It's like "back in the days", where devices had a physical menu button, which you sometimes hit and nothing happend or you discovered the menu.

To make it even clearer to you, my setup:

Navbar Back: Back

Navbar Back (longpress): Kill App

Navbar Home: Home

Navbar Home (longpress): Search

Navbar Recents: Recents

Navbar Recents (longpress): Jump to last active App

Hardware Back: Back

Hardware Back (longpress): Kill App

Hardware Home: Recents

Hardware Home (longpress): Sleep

Hardware Home (longpress) on Lockscreen: WAKE

Yes, some actions are binded redundantly, just to increase the space even more.

Hope now you are enlighted.

And it would be lovely if you could just try it and report if you have got the same issues with the navbar. Thanks in advance. :good::cool:

---

I just booted into recovery to check the responsiveness of the menu buttons of TWRP and they work properly and without any flaws. :/

It really has to be some Software thing...

I am not sure about how this is handled code-wise, but maybe the "touch-responsive" zones are not linked with the graphical representation of the navbar, i.e. the black bar. Maybe due to changing the screen density, the responive-area is messed up? :confused:
[One (M7) Original Android Development] rpmccormick:
Thanks. I do understand your setup better, and can agree with some of your reasoning. I did already try it out for you and reported in your other thread. 36dp seems to work decent enough for me, 30 and 24 don't seem to (but for me I have no problem using the Logo2Menu either).

The biggest problem I have with the Menu-Overflow ... is that it just doesn't work right! A few apps have menu's and the overflow still doesn't appear (launchers where they did that on purpose mostly) and tons of apps show the ... even though pressing it does nothing. That drove me nuts before Logo2Menu was created. It is less of an issue with an always on NavBar for sure. Also not an issue for properly written/updated apps, but even Google hasn't updated all of theirs, so wtf.

FYI here is my setup... I don't even use double clicks, but I do use PIE:

Sweep2Wake

Back (press) = Back

Back (hold) = Recents

Logo (press) = Menu

Logo (hold) = ScreenOff

Home (press) = Home

Home (hold) = GoogleNow

PIE = Recents/KillApp/LastApp, Menu/WidgetPager, Toggles/ScreenShot/Search
[One (M7) Original Android Development] fifthelement:
Due to problems I was facing with this ROM , I switched to a Google edition ROM and I am much more happy , it is definitely much faster and snappier and sounds are great again and no black screen on games anymore. although it lacks the customization of slimbean.
[One (M7) Original Android Development] spaboleo:
Personally I am not a huge fan of sweep to wake, as when the phone is lying on it's back on the table the sweeping gestures makes it "spin", due to the nature of the curved back and it's low friction :(

I use this feature fairly often as reaching up to the Powerbutton is just annoying, even with normally sized hands.

(Of context: As mentioned before this is what I envy iPhone users for. Flat back, solid position on any even surface and a huge button to wake up the device on the front of the device.

There are a few Android devices with phyiscal homebuttons, but most of the time the back is curved or there is a camera that makes that whole experience feeling shaky or flimsey...yeah it's "complaining" on the highest possible detail, but heck it's a 600$ device ;) ...and yeah I know it's always about compromises ;) )

What really bugs me the most about the HTC One.

Why the hell didn't they turn the HTC Logo into a proper touch button that is covered entirely. :rolleyes:

---

Off notice:

Batterylife is amazing! :good:

I am now at 40%, which means a 60% drop in 26h with 3.5h of screen-on time :)
[One (M7) Original Android Development] rpmccormick:
For me, both ARHD10.1/2 and Slim b7 are as snappy as I could ever tell the difference on. Stock and Slim b6 were both a little laggy, but b7 has zero lag in my eyes. Sorry your game doesn't work with it. Hopefully that will be fixed down the road.

That's very interesting about your flat-back desire. I can easily see how that would be very important to you and others, but I had never thought of it as I have never tried to use my phone while it was sitting on a flat surface. I always hold my phone when I use it. I suppose I have at a restaurant while waiting for food, but in that case I always place my phone on top of my napkin and it does not rock bad. I also have a dock at my bed and desk, so I use it standing sometimes too, but 99% of the time the screen is on, it is in my left hand.

Again, I'm quite happy with Logo2Menu. It does blow my mind that HTC didn't make that the norm, but the hacked top-half fix works absolutely perfect for me. I was an owner of the original G1, and the menu button for that was a sliver just below the center of the screen, so the dimensions of the Logo2Menu touch area feel right at home to me. You should try it for a week, I think you will become quite used to it.
[One (M7) Original Android Development] spaboleo:
I highly recommend you to do a full wipe including data and the sdcard!

I had like 3h of batterylife before and I guess even though I wiped (of course) before flashing slim bean I guess there have been some residues of my "flashing-orgy", when I was trying to find a good rom ;)

Boot into TWRP (guess there is something similar for clockwork…)

Go to "Wipe" -> "Advanced Wipe"

Cache, Dalvik Cache and System should already be checked (normal wipe/factory reset). Additionally add "data" and "storage/sdcard".

(!! Warning ALL data will be erased, including nandroid/TWRP backups and everything stored on your sdcard, so backup accordingly beforehand !!)

Perform the wipe and stay in recovery

now use ADB to push the slim bean rom file, as well as the additional app package (aroma installer) to the sdcard using:

"adb push path/to/slimbean_rom.zip /sdcard/" and

"adb push path/to/aromainstaller.zip /sdcard/"

(change paths accordingly or drag and drop the file into the terminal or cmd.exe)

in TWRP flash the rom and the addons as usual, reboot and be happy

:good::laugh:

With that you get a 100% clean install of slim bean (well, to be fair, any rom...but why switch? ;)) without any remaining elements of other roms that might interfere with your desired installation.

I am just amazed how much of an impact that had on performance and battery life!

Especially my battery life increased to 36h with 5h of screen time, without sacrificing anything!

Positioning / GPS / Syncing / Mobile Data / Wifi always turned on.

When I just did the normal wipe and flashed slim bean it was somewhere around 3h of screen time and I got 20h max. outof it under the very same conditions.

Thanks for this great rom! :good:
[One (M7) Original Android Development] jamaiquino:
Is anybody else having issues flashing gapps packages? Neither update nor official works.

Or does anyone know of a similar issue, maybe you have an idea?
[One (M7) Original Android Development] cvsolidx17:
Anybody having issues in this build where the person on the other line cannot hear you?
[One (M7) Original Android Development] wikie:
hello, I wanted to ask what is the sdandert lcd pixel density? I now have the setting of rome but would like the normal lcd density haben.Bitte for help

Gesendet von meinem One mit Tapatalk 2
[One (M7) Original Android Development] wikie:
hi guys please can you pixeldichte me the standard say? now I have the setting is the normal density?
[One (M7) Original Android Development] Flinny:
Around 480 is default if I remember.
[One (M7) Original Android Development] wikie:
thank you, one question I have, the smart remote tv remote control will always end that is with you, too?

and where do I insert my bootanimation I see it?
[One (M7) Original Android Development] jamaiquino:
can someone verify the checksum of the Slimgapps ver 7 for me

this is what i created

235C38E88A8EDADADAADD422D443BDB0
[One (M7) Original Android Development] spaboleo:
samesame...guess part of the issue is that you can choose between the themed and unthemed version?

But what really confuses me at the momen:

I can't get Google Maps to update to the newest version :(

And today it kept my phone awake for 1h, even though I didn't use maps or any map-related program at all.

Weird :confused:
[One (M7) Original Android Development] dc4:
Infrared does not work for non-sense roms right now.
[One (M7) Original Android Development] jamaiquino:
Did you quote the wrong person?
[One (M7) Original Android Development] jamieunit:
7.2 is out

Just bout to install

Edit: running good, sound quality is better but I think they lowered the gain, DSP works now so can adjust to your own ears.

YouTube also didn't load the vids so uninstall restart uninstall restart then install market version.

Sent from my One running Slim Bean
[One (M7) Original Android Development] spaboleo:
no.

It's the same as flashing gapps...doesn't really seem to have any effect.

And I think all this is related to the theme-switchable apps...
[One (M7) Original Android Development] jamaiquino:
i get a "failed" "unable to open zip" when i try to flash it.

its been happening for zips that arent ROMs for me. this must be an issue someone knows about.

and i wish i could check md5, but it seems i cant get an answer
[One (M7) Original Android Development] spaboleo:
Well...just don't flash regular gapps.

Read:

http://www.slimroms.net/index.php/downloads

They are included in the addon-packs...
[One (M7) Original Android Development] spaboleo:
I just installed the weekly build 7.2 with the latest update of the aroma addon-package.

(btw: is it okay to flash those updates "dirty" over build 7?)

What I really can't get my head around is, why Google Maps doesn't update to latest version. :(

I still have got the "old" Layout and the old map-style.

If I open Google Maps -> Settings -> About it says:

version 6.14.4 (#6140400)

And the Play Store tells me that the app is up to date.

But the version from the 11th July has an entirely different interface than the one on my device. :confused:

edit:

And I can't install the new gallery.apk, which includes the camera which is supposed to be leaked from 4.3 :/

It just says something like "installation failed" :(
[One (M7) Original Android Development] rpmccormick:
Me too on Google Maps... do you think it is ROM related? I thought I just didn't get the update yet... I only got the updated Chrome with new notifications this morning, and that came out with the new Maps.

Did you try pushing the new maps apk?

Can you link to this new gallery apk (and to a source for the maps.apk if you do try that)?
[One (M7) Original Android Development] dc4:
If you are having issues installing the new maps, uninstall the current version from tb and download the newest version online or in the themes and apps forum and install it manually. Nothing to do with the rom.
[One (M7) Original Android Development] spaboleo:
But why do I need to install the APK from a third party?

Why is it not possible to install this version from the Play Store, even though, the previous on the play store page show the new layout, as well as the update date 11th july, 2013?

// edit:

Forgot about the other question :)

Dind't try pushing the map, as I am quite hesitant when it comes to installing third party apks.

Only exception: If I know I can trust the source...I got it from a german website:

http://www.smartdroid.de/kamera-app...download-photo-sphere-ab-android-4-1-nutzbar/
[One (M7) Original Android Development] rpmccormick:
I am so mad at my phone right now!

I was supposed to take my mom to the airport super early this morning. I set 2 alarms and she called me 25 times but my phone did not wake me up. She drove to my house to get me out of bed. On the way to the airport she called me again to test, and my phone showed her picture but did not ring at all!!!

I thought it might be "Quiet Hours" even though it specifically says that calls will still ring. On the drive home I disabled quiet hours, tested an alarm which worked, reenabled quiet hours, retested the alarm, and it worked again. Then when I got home I called myself and my phone didn't get the call at all even though it had full signal. I called a second time and my phone rang fine even within quiet hours. I disabled quiet hours anyway, just in case.

So unfortunately I cannot reproduce the issue, but I know for sure that on the ride to the airport, the phone was showing an incoming call on the screen without making any noise, and the volume was on full (adjusted from 80% to 100% while it was showing the incoming call, but not a peep from it). I suspect the alarms made no noise either, but I could have slept through them I suppose.

I do know what to do, but I cannot let this happen again! I have to be able to hear my phone when someone calls me 25 times in a row. How could this happen? running official b7.

PS: The sound mode was definitely normal+always vibrate as it always is and I almost never change it. When my mom called on the way to the airport, it did not vibrate either, it turned on the screen and shower her picture, but nothing else. I, am, so, mad, right, now. :(
[One (M7) Original Android Development] jamaiquino:
we are in a slimbean thread, i'm flashing slim everything.

notice above that i said both the update pack and the official wont flash?
[One (M7) Original Android Development] spaboleo:
I don't like the tone of you messages.

Good luck :good:
[One (M7) Original Android Development] s33d1ing:
Is anyone else having FC on Google search? As soon as I search for something, it crashes. And yes, I have uninstalled it, rebooted, installed then flashed gapps again. It still crashes after that.
[One (M7) Original Android Development] Flinny:
Seems to work ok here... is it a voice search/text search/both that cause the FC? can you dump me a logcat?
[One (M7) Original Android Development] s33d1ing:
I downloaded and flashed the new slim gapps uploaded yesterday before making a logcat hoping that it would fix it, and how Google Now doesn't install via the gapps. I can still download it from the play store though. Ill have to look into it when I get off work and see if I can figure it out.
[One (M7) Original Android Development] spaboleo:
Yep!

Hat the same issue with Google Search FC'ing.

It started the app itself...so I saw the now cards, the search bar and my recent results...even if they were performed on a different device.

But if I manually tried to search via the app it crashed.

I flashed build 7.2 and the addon-aroma-package including all the google apps "dirty" over my build 7 install without wiping.

I then removed maps and gallery as I couldn't install the newest version and upgraded those by manually installing the released apks.

To solve the issue of the force close search I removed it using TianiumBackup (it's highlighted red) and restored my TitaniumBackup of it from build 7 and now it works like a charm again.

There is either something wrong with the dirty flashing or the search app in the newest build.

s33d1ing & Flinny, did you wipe or even full reset before flashing 7.2 or did you as well just flash it dirty?
[One (M7) Original Android Development] s33d1ing:
At first, I dirty flahsed and then I tried a clean install. However I just did another clean install with the newest gapps and its working now. I think the problem was when they moved it to system/app instead of data/app. I don't know why dirty flashing the new gapps didn't fix it, but a clean flash with the new gapps fix it.
[One (M7) Original Android Development] jamaiquino:
i didnt like what you were insinuating. I tried my best not to respond how i initially thought to because i appreciated that at first you were trying to help. In that message it seemed like you thought i was stupid enough to flash regular Gapps on slimbean.

i dont know what i did, but i flashed cLock last night, then decided to try SLIMgapps again, and it worked (after 10 days of trying).

thanks for trying to help
[One (M7) Original Android Development] spaboleo:
Thanks! That's good to know! :good:

Gonna give it a try...even though setting everything up from scratch is quite a hassle. :(
[One (M7) Original Android Development] s33d1ing:
I know right. But I've set up slim so many times, it doesn't take long to customize it back to the way I like it :p
[One (M7) Original Android Development] spaboleo:
Hehe...yeah, but still...downloading, titanium-ing, nandroid-ing, pushing, wiping, flashing, addons-aroma-ing, setting up the system...and then all the apps..

1.5-2h :(

at least i didn't have good experience with letting titanium backup automatically restore everything :/

it always somewhere went wrong...

So I tend to do it manually :/
[One (M7) Original Android Development] jamieunit:
New updated slim gapps are out

Sent from my One running Slim Bean
[One (M7) Original Android Development] rpmccormick:
As long as your market works, you can just delete every other GApp and download them each from market these days. Then you can use Ti or a root FM to make them system apps if you really want to (I wouldn't bother). I had trouble in earlier builds with the 3 separate DarkSlim apps, but the add-on package apps always worked fine for me. Build 7 is my 3rd "dirty" flash and I haven't move to 7.2 yet. I deleted Maps cause it wouldn't update, but then the one in market was old too for a few days, and then it finally updated. I think it was just a slow roll-out and may have updated fine had I left the Slim Maps.
[One (M7) Original Android Development] spaboleo:
Set it up from scratch last night and got really disappointed that it didn't solve the Search problem for me.

Then I saw your post and was mad that I didn't check the website again... :angel:

Thanks :good: :laugh:
[One (M7) Original Android Development] julllleee:
What version should you use? Thera like 4 doften for the m7

Thanks in advance
[One (M7) Original Android Development] spaboleo:
http://www.slimroms.net/index.php/supported-devices

If you are in the US it depends on the carrier...otherwise the international "UL" version.

---

weird...even after setting everything up from scratch again and using the updates slimbean addons and gapps, search would not want to work :(
[One (M7) Original Android Development] jamieunit:
Have you tried just the ROM and gapps nothing else?

Sent from my One running Slim Bean
[One (M7) Original Android Development] xSilas43:
To be honest I tried titanium and had issues from the start. Used go backup pro, upgraded to the premium version for free for batch backups etc, and haven't had a problem since, you can even backup to drop box or box.net
[One (M7) Original Android Development] julllleee:
I have this weird problem that when i turn on the phone it stays black. I can still unlock it but the screen is black and the buttons are on, If i touch the screen i can feel the unlock grid, The screen sometimes turns on for like 0,1 sec and then turns off and this happens. It's like this 90% of then times i tries to start it, Does anyone know what the problem is? thanks in advance !
[One (M7) Original Android Development] rpmccormick:
DEVS: I have a long-standing issue to report. When I use Google Hangouts for video chat, I cannot hear the person. We both see each other and they hear me, but I hear nothing. I finally got around to trying to fix it by swaping the APK but to no avail. I did not try it on another AOSP rom, but it does work on ARHD and stock, not in SlimBean 6x/7x
[One (M7) Original Android Development] jamieunit:
7.5 is out. Does the op not get updated anymore?

Sent from my One running Slim Bean
[One (M7) Original Android Development] spaboleo:
Hey,

to be honest...no haven't tried.

But I can't imagine something interfering with it.

I use Titanium Backup since Android 1.6 (yes, still got my SMS from back then :good::p), and never used the batch-functionality.

Each time I go through my whole app list and select the apps manually. So I don't restore apps that synchronize by themselves, such as evernote or dropbox.

And in general I don't restore Google Apps and/or System Apps...so it should basically be the same as a "clean" install with just the rom and gapps :)

Anyways...gonna give it a try with 7.5 later today.

Thanks :good:
[One (M7) Original Android Development] jamieunit:
Delete
[One (M7) Original Android Development] spaboleo:
Now I just flashed the 7.5 weekly ontop after wiping the caches.

No reflash of Gapps, as there was no update anyways...and everything seems to work fine. :good:
[One (M7) Original Android Development] spaboleo:
I couldn't answer the call I just received becasue the screen wouldn't turn on :(

This sucks badly...
[One (M7) Original Android Development] Flinny:
I can't say i've had this and I've been using my phone quite a bit, is there anything non-standard with your setup? Any Tweaks/alternate kernels etc?

If not... any more info/logs available to help looking at the problem?

Nick.