Search results

I can't get this working. For some reason my device is always on 300MHz and no Deep Sleep. :confused: I checked BBS, and it is a wakelock called *backup* that seems to keep the device awake (Awake, Screen off) 100% of the time. The only solution I've found is to disable the backup option in...

Have just got my hands on a Moto E... unlocked the bootloader OK... but trying to get TWRP on and just going around in circles. EDIT: apparently the 1 hour of reading all the threads wasn't enough... needed 1 hour and 10 minutes :o

Good to know... I have saved that file to my dropbox so I can attempt to download on my 3rd world interwebbytubes ;) Thanks for your help... I'll give SlimKat a go... This Omni LP ROM has some issues (Torch FCs, doesn't save WiFi passwords??!?, connection issues etc)

Thanks for the quick reply... it seems a lot of the HOX stuff is dead or broken these days :( I have got as far as unlocking the bootloader, installing a (very) yellow version of TWRP (v2.8.5.1.BiG) that apparently put me onto the "new layout"... and I actually installed Omni, as that seemed to...

My beloved nexus4 has developed a giant deadzone across the middle of the screen, rendering it pretty much unusable. A colleague has gifted me an old HOX and I'm trying to get a custom ROM on it. Being an old Slim Team Member I'd like to try it out... But it seems teemo's download server is no...

This seems to be a "feature" of 6.0.1... :rolleyes: That is to say, it affects ALL 6.0.1 ROMs as far as I can tell... even stock 6.0.1 (The same thing happens on my Nexus 7 2013). Even using the option in "Developer Options" doesn't work. Whether it will be rectified in the future or left as...

Seems the latest build is missing the kexec-hardboot patches... so no MultiROM support on r217 :( I assume this is due to r217 being based on a different kernel branch to older builds and will re-added in the future? :confused:

Hi Roland, Firstly, thanks for the awesome guides and videos... VERY easy to follow :) EDIT: seems it was just me being a derp... all good ;)

Fairly sure (99.9%) it is... But the whole TRIM thing happened so long ago that I can't remember exactly what occurred... From memory, it was originally an OEM thing, some devices got it, some didn't... Then it was merged into AOSP so it should be in android by default... You don't need to do...

Hey guys... Try not to get too excited... I've just popped back to New Zealand for a quick visit and thought I'd give you all an update... I'm pretty much going to be based in Indonesia for the foreseeable future... And due to the nature of my employment (pilot with a small regional airline...

As Twiq had mentioned... It is an unofficial build of Slim, so unfortunately we can't help... In any case, I have no idea on that device... It is using a totally different chipset (Broadcom) to what the i9100 is using... I suspect that like the i9100, Samsung won't have released the proper...

Honestly don't remember about 2.2... It's very old and unsupported now... As for Google search, can you not just long press on the Google search widget and drag it to "remove"? I think default launcher is Nova isn't it? Sent from my Nexus 7 using Tapatalk

Settings->Battery usage stats a fairly useless really... As always... as mentioned about 53495021421 in this thread... 1. Install BetterBatteryStats (get it free on XDA forums!) 2. Identify App/Process generating Wakelocks 3. ??? 4. Profit! What occurs at 3. is really up to the user and...

I did?? Must have been a loooooooooooooooong time ago... coz I don't remember!! haha :silly: To be honest, the sim toolkit thing requiring a PIN is some weird AOSP "security" invention... it was implemented, I believe, because some STK functions can cost users money (prepaid recharge, premium...

Flashing a custom PIT isn't without danger... there are risks that you could brick your device if something goes wrong during the flash... having said that, several people seem to have done it without too many issues... Using a custom PIT shouldn't break ANY custom ROM flashed via recovery...

Default partitioning on the n7000 is for a 2Gig /data partition... so yes, you're limited to 2Gigs for App internal storage... unless you either repartition using custom PIT file or try and move stuff to SDCard... Not sure why Samsung did it like this... but I guess these devices were around...

Ok... so based on cgk's "workaround patch"... I have created a new build... :good: I have upped it to dropbox... and have uploaded it to goo.im as well... I would appreciate it peeps could try downloading and testing... hammer away at the sdcard and see if you can reproduce the sdcard bug...

Ok... so based on cgk's "workaround patch"... I have created a new build... :good: I have upped it to dropbox... and have uploaded it to goo.im as well... I would appreciate it peeps could try downloading and testing... hammer away at the sdcard and see if you can reproduce the sdcard bug...

Probably not... #blameSamsung... they messed up the audio subsystem on this device... and then nevere bothered to give us the details... http://www.killermobile.com/forums/total-recall/9507-total-recall-on-sg2-9100-runing-cm10.2.html Granted that is for CM10.2... but basically, most AOSP Based...

Have you tried clearing the data/cache of the Gallery app?

Fairly sure that MHL is broken on all custom AOSP ROMs on S2... no drivers... #blameSamsung Probably because this isn't beanstalk... or c-rom... :P That's nice... I want a new car... Next time... try including getting some logs... otherwise we can't debug... Also, did you install minimal...

Better find a .tar format kernel to flash via Odin (or Heimdall) then... or flash Stock ROM via Odin/Heimdall and start again...

You cannot use ROM Manager... on n7000, Kernel and Recovery are one single partition... you have to flash a Kernel with the Recovery that you want... As stated, flash Raw Kernel, reboot recovery... Flash ROM + Gapps

Possibly the CWM recovery on Philz kernel is too old... I forget the exact version number, but you need an up to date recovery for the flash script to work... try flashing the raw kernel for KK... then reboot recovery again and try flashing... 3rd answer in the FAQ in the OP's...

Yeah... best to flash the latest stock first... then start flashing custom ROMs

In case anyone needs it... I have uploaded the latest Polar Beat 1.0.3 apk to a mega account... NOTE: this was downloaded from 4shared from an unknown/untrusted source... I've just taken the liberty of mirroring it on mega... as 4shared is a pain in the arse to download from these days...

Ok folks... seems some people haven't quite got the message yet... with regards to the "Clear All" button in the recents window: 1. It is not required... Messing with Android Memory Management is a "Bad Idea"™ 2. It is not required 3. It is not going to be implemented 4. It is not required 5...

what area do you live in? I can see it fine here... possibly region restricted by Blackberry? Nope... not going to happen... given that a large number of people have trouble reading basic instructions and/or finding simple menu options... I am certainly not going to recommend that people start...

Well.... look what arrived today... ;) Finally got my hands on one... this should hopefully make the dev and testing a little easier :) I won't guarantee a bug free ROM tho :p

SlimOTA doesn't update anything... it just downloads the files... you still need to flash via recovery... suggest you head over to http://www.slimroms.net and read the installation instructions... you'll also find the updated Gapps packages there NOTE: I wouldn't recommend dirty flashing from...

Firstly, this isn't AOKP ;) Secondly... if using Nova... Nova Settings -> Look and Feel -> Screen Orientation :good:

What recovery are you using? And have you actually checked the sha1 sum of the downloaded file vs. the one listed here? TIP: You can use sha1sum FILENAME on phone using terminal emulator/adb shell

Probably not... I've looked into this before... and WhatsApp is bypassing the Android notification system and playing it's "notification" sounds directly... You'd need to set the whole audio subsystem to silent to prevent this... BT changed a HUGE amount... Google moved from BlueZ bluetooth...

Really dependent on your particular device, network and location... you'll need to experiment to find the best baseband... PROTIP: If it ain't broke... don't "fix" it! ;) Also... don't mess with RIL... if you flash a modem/baseband... make sure the package doesn't include any RIL .so's included...

:rolleyes: I'll just check the logcat you posted to find out what is causing it... oh... wait... :rolleyes: :rolleyes: Thanks for the tip... unfortunately, I have no idea when I'll get a chance to look at it... but hopefully it won't conflict with our hardware key rebinding stuff...

I attempted to replicate this (granted, I was using i9100)... and couldn't... waited till screen went off, pressed home, back to home screen... waited till screen went off, pressed home, back to home screen... are you long pressing home? or just quickly tapping it? I'm still trying to source a...

Short version: So... as it turns out... it was just the graphics library (bootable/recovery/minui/graphics.c) not liking 32bit PNGs... :confused: :eek: I converted them to 24bit PNGs and they now work perfectly... :highfive: :victory: :good: Long version: So after spending copious amounts...

It is charging... Just the animation is broken... I just haven't bothered fixing it, as it is purely cosmetic, and I never charge with the phone off anyway... Only affecting i9100, n7000 and maybe since of the other Exynos4 devices... It is a complex relationship between recovery, kernel...

Yep... we know exactly why it is happening... because you followed proper bug reporting procedure and posted a logcat of the crashes which we can look at to diagnose your issues... oh... wait... :rolleyes:

Totally KitKat issue... Not related to Slim or n7000 Sends the PBAP is broken or something... Well known issue for pretty much all devices on 4.4 with a lot of carkits.. Sent from my Nexus 4 using Tapatalk

You could try learning how to report bugs... :rolleyes: Sent from my Nexus 4 using Tapatalk

Ok... can you guys please test this build: https://www.dropbox.com/s/3hnd9a75mh66ma0/Slim-n7000-4.4.2.build.2.5.RC1-UNOFFICIAL-20140128-0642.zip It *should* fix the issues with hardware keys :good:

Then the drivers on your computer must be bad... try uninstalling all the phone related drivers and then reconnect the device... I connect to linux build box...

Are you sure about that?

So when you connect and do "adb devices" you don't get any devices listed? I'm unsure how/what you're expecting to see... and where you expect to see it? What exactly do you mean by the "computer detecting phone as USB debugging device"???

The rebinding code isn't broken... I just didn't realise that an RC1 was going out and I hadn't got around to creating the device overlay for n7000 to specify which hardware keys it has... As I only have i9100 and have been doing all my testing on that... The default is "none"... So that is...

So really... How to make users learn to read? :rolleyes: TWO posts above yours FFS... *smh* :rolleyes: I'd guess that you can't install on 4.3... Probably missing frameworks, libs and/or settings etc Check logcat to find out why it's crashing... Sent from my Nexus 4 using Tapatalk

Did you even bother to try searching the thread? Sent from my Nexus 4 using Tapatalk

No... that was BlueZ stack... AOSP switched to Bluedroid... caused a lot of issues with BT :( It would appear that BlueZ is attempting to create a compatible replacement for Android... not sure of the status on this... but maybe in the future users can drop BlueZ back in and all their **** will...

Add "network mode" tile to QS... You'll notice it has the "settings icon" on it when you add it to the layout editor... Tap the tile and you can select any combination of 2G, 3G and/or 2G+3G... Then each time you tap the tile in QS, it cycles through the modes... NOTE: it may take time to...