Showing posts with label thread. Show all posts
Showing posts with label thread. Show all posts

Monday, 12 October 2015

Custom ROM thread



Hi guys, i was thinking of making a custom ROM for the P8. Nothing too complicated though, just a stock 5.0.1 AOSP with a reizable nav bar, just to be a stock experience. Anyone interrested ? Devs ? I notice that bootloader is unlockable, so the rest should not be hard :) PM me.



Wifi not scanning (plz read the whole thread)



I have a in focus m2 3g
I had used exposed modules like GB WiFi was working fine
After couple of weeks my WiFi won't scan also I did scan sometimes
And whenever I used to turn on WiFi screen used to go black
I tried reset ...it worked for like 10min then I faced the same issue
I also tried flashing now the WiFi doesn't scan ....actually it does scans but the screen going black frequency has been reduced
According to me it ain't a hardware issue
Experts plz help me fix this
Thnx



Saturday, 10 October 2015

New Games Thread!



A few new games for android a couple years from now (List)
1. Hotline Miami
2.Hotline Miami 2: Wrong Number
3.NFS: No Limits
4.GTA 10th aniversary series
5.Max Payne
6.FIFA 15 UT
7.Mortal Kombat X
8. Half-Life 2
9.Portal
10.Pirates
Please add More Entries



Benchmark Thread! [Post Your Benchmarks]



This is obviously not a gaming device or a high end device but still performance might be different in different ROMs or kernels so
Mine is 19198 (Not impressive)
Current ROM : CM 12.1 Snapshot Latest Builds
KERNEL: CM



Blu Studio 7.0 Official Thread (Variants 1 and 2)



I've looked everywhere on Xda in search of a support thread for the Blu studio 7.0 I and II. Couldn't find either. So I figured I would create one. If I have created it in the wrong section please move it to the correct section. Thanks

The Blu studio 7.0 is a "low end" android device that comes carrier unlocked and supports dual Sim. You can obtain it for GSM and CDMA networks. As the name states. This device offers a 7 inch screen and is considered a phablet. I haven't ever used the first version of the Blu studio 7.0, but the specs are not that great on paper.

The second version has 1gb of ram and a quad core processor. On paper the screen specs aren't too great, but I've not had any issues with the way it looks. The worst part of this phone is no flash, and camera quality is hit or miss. I don't use the camera too much anyways other than making YouTube videos for my blog. So it's not a huge downfall.

The operating system on the 2nd variant runs android lollipop and I've read rumors that it's going to be upgraded to marshmallow when it's available. Most of the already released Blu devices will not receive android 6.0.

Root is very easily obtained on the Blu studio 7.0, if you need help obtaining it. Just ask below and I'll assist you in obtaining root. You don't need a computer, and it's just 1 click from your phablet.

The studio 7.0 supports 4g but not lte which may be a downfall in your eyes, but 4g is fast enough for what I do so far.

This phone is very very responsive and hasn't lagged at all for me. I consider myself a power user. I am constantly using multiple apps all at the same time (Google a sense, analytics, Fanduel, WordPress, multiple websites opened, texting app, tapatalk and a few others all running in the memory with no lag).

If you've ever used a lower end device. You know that one of the most annoying plagues on them are keyboard lags. I absolutely hate when I have to slow down my typing because the keyboard can't keep up. It makes me want to smash phones. This keyboard is great. Never lags, and never freezes.

For under 150$ usd. I'd buy it again.

___________

If you need any help with your Blu 7.0 this is the thread to ask for it. As well as asking, please give support for this phone as well. As of right now. I don't believe that there are any custom roms for it yet. If you know of any custom roms for this phone. Please post them here as well.

Sent from my BLU STUDIO 7.0 II using Tapatalk



Thursday, 8 October 2015

Phone hardbricked after following "[Solved] Secure Boot Error" thread. What do I do?



I followed the one click root method, which worked out well. After that, I installed su, flashify, and twrp. I then tried installing a custom rom, but upon booting into recovery mode, I received the Secure Boot Error text. It wasn't too big of a deal since I could still take out the battery, put it back in, and boot normally.
But, after seeing this thread:
http://forum.xda-developers.com/lg-g...-boot-t3054977
and how simple the instructions were, I proceeded to give it a shot. I entered in the 4 commands, powered off my phone, and attempted to boot into recovery mode. But unlike before when I booted into recovery mode, nothing appeared. No lg logo, backlight power, nothing. It's acting exactly as it would as if there wasn't anything powering. Now I'm stuck with a bricked phone, and sincerely need some advice on where to proceed next. Could someone help me?

Oh, btw, when I plug the phone the computer, I do "the device was successfully installed" message. The phone appears in device manager, under Ports as LGE AndroidNet USB Serial Port or as LG AndroidNet Phone under devices and printers. It doesn't appear under This PC at all.



I think I may have "killed" my HTC (Specifics in the thread)



Ok, so I'm very new to using bootloading and fast boot and all of the other developer tools, and I seemed to have killed my HTC.

I downloaded the rashr flash tool with the hope of being able to install the CyanogenMod rom to my HTC One X. Using the rashr flash app, I selected the option that allows you to flash a kernel on your phone, and I selected the img file that I downloaded which was the latest nightly img. Afterward I went into the command prompt and typed in adb reboot bootloader. From there I haven't gotten any response from my phone at all. The screen doesn't turn on, the small light indicator hasn't lit up at all, and I know the batter is close to fully charged, but there's nothing happening. Did I kill my phone? Can anyone help me out with this problem?

Not entirely sure if the phone is brand new, but my uncle bought it for me, he said it was unlocked, though I'm assuming he meant SIM unlocked because when I was able to get to the boot menu, it showed that it was still locked at the top. It had all of the packaging contents and the screen protector - so it's "like new"

The only clue I have to there still being some sort of "life" in this phone is this weird device that shows up in the device manager under "Other Devices". It says "QHSUSB_DLOAD", but no information can be pulled up about it

I hope my story is detailed enough, I can elaborate more if need be. Please go easy on me, I'm a nub but I want to learn this stuff xD.



Wednesday, 7 October 2015

[Camera] Tweak thread to make M9`s camera even better :)



First of all, I would like to thank all those guys from "Photos Taken With M9" thread.
HUGE GREAT BIG AWESSOME THANKS go to @starbase64 ; @defcomg ; @hamdir !!!
SO THANK YOU MATES!!!!


Since HTC made a bad software, that compress data from chip and creates jpeg, many of us hoped for something new, something better. With every update we prayed for better noise control. Some prays were heard, some were not. Theese hard times a few heroes, that see thru codes and hacks found a way how to make our photos better. Enough talks, lets go for it!

DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR PHONE USING SOME OF THIS HACKS

Build.prop tweaks:
For better noise controling, faster shots etc.. :)

How to: In system folder is build.prop file. Open it (for example) in ES file explorer (you have to check root explorer) and simply add theese lines at the end of it. :)

persist.camera.qcwnr.enabled=0 / this command removes HTC`s color noise reduction.
camera.eis.enable=0 / this command disable electronical image stabilisation
persist.camera.snap.format=1 / this forces subsampling to 2:1 (default is 2:2) , about subsampling : http://www.cerious.com/help8sp1/jpeg_sub_sampling.html
persist.denoise.process.plates=x / REPLACE "X" with 0,1,2,3 where:


Quote:









Y = Luminance Channel
CBCR = Color Channels

0 = CAM_WAVELET_DENOISE_YCBCR_PLANE | Quality Priority Color & Luma
1 = CAM_WAVELET_DENOISE_CBCR_ONLY | Quality Priority Color only
2 = CAM_WAVELET_DENOISE_STREAMLINE_YCBCR | Speed Priority Luna & Color. This is the default profile used BTW
3 = CAM_WAVELET_DENOISE_STREAMLINE_CBCR | Speed Priority Color only.






LONGER EXPOSURE than 2s

This tweak is about getting longer exposure in manual, RAW mode.
I am able to get 4sec long exposure. Some are able to get 4.9.

Its complicated, because it depends on firmware version of your ROM.
But you can do it by your own using HEX editor.

1. You need file /system/lib/hw/camera.msm8994.so
2. In HEX editor find B4 EE E0 8A and change it to F4 EE 60 0A
3. You need also /system/vendor/lib/libmmcamera_t4ka7.so
4. In HEX editor find B4 EE 61 8A and change it to F4 EE 61 1A
5. Save those files in your SDcard. Backup original files. Delete original files from those directories and paste those new. I dont know why, but overwriting didnt worked for me.
6. Find res_ctrl.conf in /system/ETC/
7. Edit it via this quote:

Quote:









M_ISO=1600,800,400,200,100
M_VIDEO=3840x2160,1920x1088,1280x720,960x544,800x4 80,768x432,720x480,640x480,480x320,352x288,320x240 ,176x144
F_VIDEO=1920x1088,1280x720,960x544,800x480,768x432 ,720x480,640x480,480x320,352x288,320x240,176x144
M_SHUTTER_SPEED=1/8000,1/6400,1/5000,1/4000,1/3200,1/2500,1/2000,1/1600,1/1250,1/1000,1/800,1/640,1/500,1/400,
1/320,1/250,1/200,1/125,1/100,1/80,1/60,1/50,1/40,1/30,1/25,1/20,1/15,1/13,1/10,1/8,1/6,1/5,1/4,0.3,0.4,0.5,0.6,0.8,1,1.3,1.6,2,2.5,3,3.5,4,4.5, 4.9
M_SHUTTER_SPEED_MARKER=1/8000,1/1000,1/125,1/15,0.5,2,2.5,3,3.5,4,4.5,4.9




I am attaching modified camera.msm8994.so and libmmcamera_t4ka7.so for ViperOneM9 3.5.0 based on 2.10.401.1.

My camera settings:

Quote:









build.prop:
persist.camera.qcwnr.enabled=0
camera.eis.enable=0
persist.camera.snap.format=1
persist.denoise.process.plates=0
In camera app:
10:7 ratio
big resolution
contrast +0,5
saturation +0,5
sharpeness -2




At the end, I would like to said that this oficial post is under construction and all critics are welcome.
Thank you and have a nice photos :cool:
and you can also check my instagram :angel: instagram.com/Majky_majk :cyclops:







Tuesday, 6 October 2015

M7 Compatible Sound Mod's Thread



Being that they have a thread like this for the M8, but the M7 & M8 have different audio files, I figured I'd start a thread here for users to list all known compatible Audio MODs for the HTC One m7...

The point of this thread is mainly for audiophiles, as well as general user info and discussion regarding all Audio related mods, apps, EQ's, and everything of the sort.

I will be adding more & more info as time goes on. As well as flashing and giving results on many , many different mods, apps, etc. Please feel free to add your 2¢.



[ROM] [T210/R] [4.4.2] Supernova [Stable] [Moved from old thread]





NOTICE: This ROM has been moved to this new thread and now features a poll. The old thread is available at http://forum.xda-developers.com/show....php?t=3214073.

Hello! Welcome to Supernova! Supernova is a KitKat-based ROM originally built from StockRom by @safariking. It runs well, and is stable. Give it a shot!

Features:
  • Comes with Nova Launcher by default.

  • ES File Manager

  • Nova Launcher

  • System App Uninstaller

  • Xposed Installer

  • Wanam Xposed (Xposed Module)

  • Pimp My ROM (Version 1.1 and later)

  • Custom Boot Animation (Broken in 1.0)

  • 4 Way Reboot


Planned Features:
  • New Wallpaper

  • Lockscreen Effects

  • Lollipop (Like that'll ever happen.)


Known Bugs/Issues:
  • Terminal Emulator crashes on startup and requires re-downloading from the Play Store


Changelog



Version 1.1 (October 1st, 2015)
  • Replaced Samsung keyboard with AOSP-like keyboard

  • Pimp My ROM Pre-Installed

  • Helvetica Neue FlipFont Pre-Installed

  • Removed Stock File Manager

  • Fixed Issue where selecting Hot Boot does nothing

  • Replaced Boot Animation with working Animation

Version 1.0 (September 30, 2015)
  • Initial Release

  • Nova Launcher

  • ES File Manager

  • System App Uninstaller

  • Xposed Installer

  • Wanam Xposed Module

  • Unintentionally Broken Boot Animation





Installation Guide



  1. First, power off your tablet and then hold down Home+Power+VolumeUp to boot into recovery (CWM, TWRP, Philz Touch, etc.)

  2. Wipe/Factory Reset your tablet. WARNING: THIS WILL ERASE ALL DATA, SO MAKE A BACKUP.

  3. When that's done, go ahead and flash the .zip you downloaded from your SD card.

  4. When that's done, reboot your tablet.

  5. Everything should go well, but it might take a bit of time to boot at first. Don't worry. This happens with every ROM. But when you're done, you should see the Samsung setup wizard. Done!





Screenshots



Ignore the Helvetica Neue font and "DIDNEY WORL" on the lock screen. I set those for myself, which means when this ROM is first flashed, you will have the Roboto font and no personal message on the lockscreen, although you can set it yourself.








Download



It is available at the following links:



Extras



Note that I made none of these and they are all flashable.



Special thanks to:
  • @safariking, for creating StockRom, which this ROM was based on.

  • Google, for making Android.

  • All the developers of the apps on this ROM.

  • And finally, @dsixda, for making Android Kitchen, the tool I used to create this ROM.




A5_UL Eu single sim (and any compatible variants) Working ROM thread



Hi all.
I'm using CM12.1 5.1.1 from 20150429. Grarak unofficial ROM.
Any Cm12.1 based ROM newer than this has bugs making my phone unusable.
-long time detecting sim card, and long time getting a cellular connection once sim detected
-SMS not sending or receiving
-no calls incoming

Which basically make it a mini tablet :(...

So far I've tried a pacman 5.0.3 ROM but found it sluggish.

Does anyone with this same model of phone have a workaround or a suggestion of a stable working 5.1 ROM?
Has anyone tried updating RUU with either success or failures to report?
I'm at a loss here and its a shame, this phone is good value for money and was working well up to this last cm12.1 build.
I really don't want to go back to 5.0, and I'm not sure any sense/stock ROM is better? Can you share positive experience on this matter?
Thanks to all devs who give their time to allow us to use and own our phones. I am grateful and in no way taking any of this for granted.
Without you we'd all have locked phones and no freedom.
And peace to all, above and beyond ALL the rest!



[Official] Fire TV 2 / Fire OS 5 (Fire TV 1) Complaints Thread (Bugs, etc)



About time we compiled a tally of what's broken, missing or just plain annoying on the new Fire TV, and what's (about to be) broken by the official release of OS 5 on the old Fire TV.

WORK IN PROGRESS

Fire TV 2: hardware shortcomings by design that many regard as substandard.

If these are important, you might need to look elsewhere.

1. USB 2.0 not USB 3.0
2. Ethernet not GB.
3. No optical port. Possible solution: http://www.amazon.com/dp/B010JQMHNW/?
4. HDMI 1.4, not HDMI 2.0, limited to 4K at 30fps.

Software bugs and annoyances, most probably due to OS 5, but yet to be confirmed.

Could be fixed either by Amazon or developers.

1. Audio limited to stereo other than for Amazon Prime.

If Amazon won't fix this one, 9/10 boxes are heading straight back.

2. External storage limited to disks formatted in FAT32.

There's no reason why Amazon couldn't enable other formats, but there's little incentive to bother. Even Macs don't support NTFS out of the box. Either format your drives in FAT32 (and split larger files if necessary) or move them to a network share. Not hard to work around.

3. Highly inconvenient to launch Kodi and other sideloaded apps.

Long story, somewhat shortened: The Fire OS only shows icons for apps obtained from Amazon's App Store. That, unfortunately, doesn't include Kodi, everyone's favourite media player, and about 99% of the reason the AFTV has a cult following. There have been two popular ways to get around Amazon's belligerence: by having Kodi launch as proxy of another app (usually Ikono TV) using Llama; or by employing Firestarter to bind it to the Home button. Both can be loaded via ADFire.

ADBFire : http://forum.xda-developers.com/show....php?t=2786505

FireStarter http://forum.xda-developers.com/fire...t-app-t3118135

It's as yet unknown whether this is deliberate (probably, as it's common to Android TV) but OS 5 appears to block the creation of local ADB connections, which has completely broken Llama's ability to intercept and switch launch requests, and partially broken Firestarter.

The best current workaround is to continue using Firestarter, with Kodi or the Firestarter launcher mapped to the Home button (single or double press), but you will need to toggle the ADB Debugging in Developer's Options each time the device is cold booted.

The good news is the developers of Firestarter and App shortcuts are on the case, but we might have to wait until OS 5 is rolled out to AFTV 1 before we see any progress:

https://github.com/sphinx02/FireStarter/issues/8

4. More to come.....