Develop Bugs

Android 2.2 (FroYo) On HTC [03 Sep 2010] (V1.6)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android on your Windows Mobile HTC Device...
Supports Blackstone, Diamond, Diamond 500, Fuze, Raphael, Raphael 800, Rhodium, Tilt 2 & Topaz
This thread is dedicated to FroYo, and NOT Eclair releases!
First things first, this post is PURELY an instruction guide for noobies that aims to reflect the latest status and downloads (give or take a day).
I am not an Android developer, I do not create any of this software... this is done by far more talented people than I. This thread is purely to collate the latest info for Android on Windows Mobile HTC devices and make deploying Android on your device as simple as possible.
If you have new information that should be added to the guide (and is relevant for ALL folks) then feel free to add to the thread and I'll update the OP frequently.
These opening few posts should have ALL the latest info you need to get started (no need to trawl through the threads).
The only time you 'might' need to look in the thread is for 'breaking news' info that is no more than a day old...i.e. The Opening Post is the place!
Credits: There are too many to mention, and many are unknown, but basically the guys poring Android to our devices should be thanked, along with all those making the effort to help others test, document, or use their work (along with those who provide answers to the same questions, time and time again). These are the guys who deserve the credit. From memory...
osamaa,
babijoee,
phhusson,
herpez
scanny
klinux
Oliwe
and many more
What's New?
Latest Update: 03 Sep 2010 (V1.6)
InitRD - 20100813-b11116a
Rootfs - 20100828-c29a486
System - XDAndroid 2.2.AOSP.3.9.10.RC.2.2
Kernel - 20100830_01302 (no debugging)
Headset support - Credits to Oliwe
3D support for Blackstone/Diamond/Raphael (Rhodium/Topaz have no 3D)- Credits to Oliwe
Gallery working - Credits to Oliwe
Touchscreen Calibration is back! During first clean install, touch each of the five calibration points CAREFULLY to calibrate your screen before installation completes. Plus, general touchscreen fixes and power off support - Credits to Oliwe
Back to basics System... stock Android system.
Takes about 5 mins usage before the system starts to speed up, so expect it to be a little sluggish for the first 5 mins.
None 3D devices may not show boot screen, so please be patient during install (screen will show black)
I'd advise that once installed, you also launch SpareParts, and configure the window animations etc to 'fast'
There is a chance that after installation, some Startup.txt settings MAY be incorrect for your device. If you discover any mistake, PLEASE let me know, I will correct asap. I need your help on this guys.
How To Install (CAB Version)
Step 1 - Prepare your SD Card
Find a nice clean SD card to load Android on.
You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
*Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
Step 2 - Download and install the CAB
Download and install the following 'full package' cab (a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid Cab button below.
You MUST install on the Storage Card. The cab file will take a couple of minutes to install Android. Please be patient.
For those that are interested the cab files does the following:
- Installs Android in the root of the SD Card
- Deploys the correct Startup.txt for the device (the user can choose their device type)
- Adds a high res icon for Android in the root of the SD Card
- Installs a shortcut in Program Files named "Android" (launches Haret.exe)
- Installs the high res icon in the registry for WM6.5 users
Step 3 - Run Android
Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
The reason the first boot takes longer is that Android is 'preparing' your device for the first time.
How To Install (ZIP Version)
Step 1 - Prepare your SD Card
Find a nice clean SD card to load Android on.
You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
*Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
Step 2 - Download and extract the ZIP
Download and install the following 'full package' zip(a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid zip button below.
You MUST unzip to the ROOT of the Storage Card. The zip file will take a short while to extract. Please be patient.
Once you've extracted the zip:
- Click Auto-Setup.exe to configure XDAndroid for your particular device
Step 3 - Run Android
Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
The reason the first boot takes longer is that Android is 'preparing' your device for the first time.
If you want to exit Android and go back to Windows Mobile, then you need to shut down / reboot. To do so with the latest Android releases, hold down the 'end call' button until you see a menu appear.
If this fails to work, then the only option is remove the battery or press the reset button.
Known Issues
Many things are still not working properly, and the developers are fully aware of 99% of them.
SDCard - Most SDCards are working, but if you the 'waiting for SDCard' message, you should try one of these fixes (and please let us know if it works)
Fix 1: Format your card with this tool http://www.sdcard.org/consumers/formatter/
Fix 2: Edit your startup.txt file and add these entries to your cmdline:
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
Fix 3: Tell your wife / girlfriend that you are about to make some modifications to her phone... change the ringtone and steal her old Class 2 SD Card to use with Android. She will never discover what you have done, and if she does, you'll be able to use Android to send texts to your former girlfriends ;-)
SDCard - A few users have claimed to have had trouble using their SD Cards after installing XDAndroid. Some of those have reformatted the SD Card, and it worked, some couldn't recover it. This is a minority of users, but be warned.
Camera - Not working
GPS - working
Battery Status - Highly problematic for most users (don't trust the capacity Android tells you, it's simply up and down a lot, and highly inaccurate)
WiFi - Working for most people, suspected to cause slight heat, definitely drains the battery faster than WinMo.
Audio - Speaker working for most people, microphone can have issues
Deep Sleep - Working for most people, but can have issues waking up (sometimes, it will not wake up)
GPRS - Working
3G - Working for most
PIN Code - Unknown
GSensor - Working (Screen only handles 0 and 270 degrees)
Bluetooth - Experimentally working (don't expect too much, but it's working for a number of users)
OpenGL ES - 'should' be working but only for Blackstone... more to follow soon
USB - Supported, but will NOT operate in mass storage mode. You can charge via USB and you can debug, but forget accessing your files by it.
Headphone Socket - Semi working (see FAQ for details on how to make it work)
Application Errors: It's very common to see 'Application (xxxxxx) is not responding: Force Close or Wait'. Click wait. I do not know the precise reason for this, but from what I can gather, it COULD be related to the slow speed of the SD Card causing the app response times to JUST be a little too slow for Android's liking, thus causing the message. This seems to happen more after bootup or wakeup when the device is busy doing stuff in the background.
Cannot choose ringtones: This is believed to be caused by the media scanner failing (due to discovering some filenames with none English characters). The best option of all is to use a CLEAN SD Card. But, if you insist on hosting other files on the same SD Card, you MUST make sure they have English character filenames.

reserved
reserved reserved reserved 2

Reserved
reserved reserved reserved 3

Reserved
reserved reserved reserved 4

I'm here waiting for the new release......

zsdja said:
I'm here waiting for the new release......
Click to expand...
Click to collapse
Zip now available
Cab will be here in the next hour... but...
This is major move from Eclair to FroYo, and it's slightly slower than the Eclair release (so far).
This is normal though, since many of the Eclair release issues where ironed out, but with FroYo we take a small step backwards before we can progress again...
This release is VERY untested... I used it for 30 mins on a Blackstone only... no other devices tested yet

There is newer system version
Hi,
there is new system version:
XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
Link: http://htcandroid.xland.cz/XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
I'm using this and works like charm!
Regards Jiri

jura55 said:
Hi,
there is new system version:
XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
Link: http://htcandroid.xland.cz/XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
I'm using this and works like charm!
Regards Jiri
Click to expand...
Click to collapse
This includes 19.7 system. You posted a bit too quickly, I was still editing stuff !

TheBrilliantMistake said:
This includes 19.7 system. You posted a bit too quickly, I was still editing stuff !
Click to expand...
Click to collapse
Hi,
many thanks for quick explanation and I'm sorry for so quick reply
Will be Sense UI included in this build?
Or where can I get Sense UI for Android?
Many thanks

looks like just an update from 2.1 to 2.2 - no bug-fixes or new working features, right?
downloading now to have a play

OMFG!! YES!!
android 2.2 has calendar sync to exchange (2007) natively!. this release has hammered yet another nail into WM coffin!
also it looks like my 2.1 install was broken - seems noticably faster and touchscreen seems to be working a bit more predicably.

sorry but where is the file.

:-D First post, Step 2 -> Biiig black button

sorry being a noob, all done and running.
Damo

Is this version include the chinese language?Thanks for the good work.
Sent from my MSM using XDA App

ok MarketPlace is now not working.....argggghhhhh

damianpadden said:
ok MarketPlace is now not working.....argggghhhhh
Click to expand...
Click to collapse
I think you can try to delete the data.img and restart the android then try again,good luck ^_^
Sent from my MSM using XDA App

lol...i just did that exact thing....remembered it from before on 2.1...thanks
Damo

thanks for marketplace fix. i too was having the same issue!

jura55 said:
Hi,
many thanks for quick explanation and I'm sorry for so quick reply
Will be Sense UI included in this build?
Or where can I get Sense UI for Android?
Many thanks
Click to expand...
Click to collapse
No it does not have Sense. Why would you want it?
You can get virtually all the same widgets from other sources. Sense is a massive resource drain (esp on XDAndroid), and on non 3D supported hardware
If you want the flipclock, you can get it from multiple places, the wallpaper, the wallpaper, and similar widgets are all floating around too.

KINO [Kin Opensource-FileManager]

Hi there!
As i said on a thread (bit long time ago), i had the intention of making an opensource file manager for the kin.
So i have been working on for two days, and i'm reserving this thread for its releases and descriptions.
It will be given as donationware, which means that you can take it for free and donate if you wish (or not to... )
SECURITY DISCLAIMER
- As you can imagine, by using this tool you have not guaranteed the operational state with your device and is provided "as is". You are the only responsable on the effects if could have on your device, even though i tested locally all the options for hours. Like you do for 3rd party non-certified software.
- DO NOT, i repeat DO NOT unplug the device nor close the program while writing or reading from the device. Errors states are unknown and you may scr3w up your flash memory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- If during the usage, it takes long, WAIT for the transmission to end. Errors are handled by the program and in the last cases there are 2 to 3 levels of error treatment, notificating you in the info box and storing a brief description on the "error.log" file when it's ultra. (I'm still human, new errors can appear).
- IF during this usage the kin gets a "Connected" window and the program is clossed without closing that window, then it's the time where you can unplug and it will reset the device communication values, pluggin again. If you reach this state without doing magic, notify it to solve the bug.
Characteristics
- Libusb driver given for the kin (needs to remove the Zune one)
- Windows (XP,7) 32/64 bits. Linux (through Mono), Mac Osx(through Mono Framework) Compatibility
- Developed in pure c# (using libusbdotnet)
- Developped in layers:
----> Usb
----> Mtp Functions
----> Mtp<->Interface manager
----> Interface
Images V0.01
Requirements
- OS:
---> Windows
------->Net Framework 2.0
------->Libusb-win32 driver(provided below)
---> Linux
------->Root mode to access the devices.
------->Mono
------->Libusb 1-0 components
---> Mac OsX (Checked with Snow Leopard, PAIN IN THE ASS)
-------> Mono framework
-------> Libusb-1.0 source (sourceforge)
----------> Modern OSX compile for 64 bits. Mono needs 32 bits. Compile (as root) with:
Code:
sudo su
./configure CC="gcc -m32"
make CC="gcc -m32"
make CC="gcc -m32" install
*Note: it takes a looooooooooooooooooong time to load the first time. be patient
*Note2: if mono yells about needing X11 for Winforms, download Wireshark for OSX, which has X11 easy installation inside (needed for it).
Download links
Kin Driver (libusb-win32): (Create one with InfWizard for the kin PID and VID)
32 bit version: http://www.mediafire.com/?0nhrdn7f5je6dcx
64 bit version: (please use above version)
Source: ***Still needs a bit more documentation, cleaning and binary testing for errors ***
* Note that i DONT have a 64 bit hardware, so i based its compatibility on the failed running in my Windows 7 (aka "this is for other architecture error")
** Note that to use this driver you MUST remove the Zune driver. I recommend to test it on a clean virtual machine first
Functions
- TreeView Kin Storage explorer (Auto Resyncs after each operation)
---> Select one or multiple items with the checkboxes next to them.
- Batch upload to the kin (to the root of the tree)
---> Select one ore more files from the selection dialog and go go go. Any file, anytime
-------> **Danger** pressing twice will upload files twice, be patient.
- Multiple file download from the kin
----> Mark any file from the tree and press "Download". The file will be downloaded to a subfolder "Downloads" next to the exe, where the tree storage has been replicated.
-------> **Danger** Folder and Playlists and other files are just logical, and have no size, so program deals with them as folders (and are created emptied in the local system at the pc)
- Multiple file delete
-------> Mark any file from the tree and press "Delete". After confirmation, the files selected will be removed from the device.
-------> **Danger** Folders are not deleted. Infobox at the bottom will inform you if a file could not be deleted.
-------> **Danger** I trickied it so the storage root could not be deleted... ahhh smart little fellas.. you were already thinking in that huh! rofl.
Known issues
- During my random tests around, i found that sometimes (dunno why exactly), the kin <-> Kino communication skips a step, messing up the mtp communication schema. The solution i used in this release was to show the root storage without children nodes. As this case is an error, you should tell me if you know a repeatable way to get it so i can retest and solve it.
To keep going with the kin, close Kino, and unlock the Connected window (slide your finger over it) and unplug & plug the usb again.
F.A.Q.
- Q: No donation button in the end?
- A: Nope. Just when it proves to be useful .
- Q: This works with Kin One devices?
- A: No. I only have access to Two (bricked) and TwoM devices, so cannot test for the little round turtle.
- Q: Do you provide a driver for Kin?
- A: Yes. It is only a bridge from the programs to the libusb-win32 functions. Unfortunately, you would have to remove the zune driver (Hardware manager) before using this one.
- Q: This bricks kin devices?
- A: At all.
- Q: This can hack the device?
- A: No. This is only a tool to upload and download files to your kin. If later it's used to hack, good anyway
- Q: Can this upload *any* file to the kin storage?
- A: Yes, binary files like exe, cab,pdf, ... will be labeled as 0x3000 (undefined filetype) for the kin.
- Q: Can i take the code and make my version called OmgKinManager?
- A: Yup. It would be a nice detail to include a little text in "about..." regarding me though

kk, apart from the above, i'm a bit stuck on the uploading procedure, doing it dinamically, not with known filesizes like i tested before.
I will try to get it to work and allow multiselection file dialogs.
Later, downloading, which is easier, as i just request files. I will try to make the selectable tree work, so several files can be downloaded at a time.
Btw, the tree is not a demo, it's my real storage, being asked to the kin. It's a long process, as i ask for the id's and their values to the kin to create a Tree structure, later parsed by the interface.
Whenever that and deletion is done, i will upload both the driver and the program/source to the public.
For Zune's functionality lost scared people, i would suggest to try on a windows virtual machine first (which i will do to test for .net framework requirements and so)

Way cool imn glad to see some progress

Nice work! I spend a lot of time on this forum reading posts and 75% of the time it's your post. You've spent a lot of time working on this project and we all appreciate it. Expect a donation from me in the near future

I'm speechless.

Hey john, you have only gotten into the media section correct? What type of things have you gotten to do if i may ask. If you want, I can help get "into" the other parts of the phone. A.K.A contacts. That's my main concern right now. I could care less of customizing the OS (which I will get to if you care to lend a hand.) Since I don't want to Say anything just yet, send me an email to [email protected]. I would like to help. I'm on my phone at the moment but tomorow I'll post how i got the phone into a writeable state (which I don't know if it still work. I've only tested twice.) If it doesn't work tomorrow, I'll donate my time during the week helping you guys. I may need to get a new battery.
P.S. It's taking me awhile to do this becuase I dont want to brick my phone. Im definately not using my enV touch!

please, read the faq above. this is not a hacking thing, but a sync one.
to be honest, i dont care about contacts cause i dont use this phone to make calls and i just wanted it to be more open. pinned apps or phone settings storage would be my only interest apart storage folder.
also, i dont want to keep secrets or long term waiting things. post what you want or dont post, but dont make it a teaser of nothing. plus i dont wanna go emailing people.

Props to you. Great utility, if it were able to get deeper into the system. Then it would be golden.

Edited for many reason

As some other forumeer seems to have gotten into the phone system, imma halt this development till acess range is shown (filesystem / storage / settings), if any.
There's no need to redo all the required mtp subsystem if we can get there by other (easier) means. OS native explorer, for example.

just go ahead and work on it in case the other guy fails. ^.^

oaktree333 said:
just go ahead and work on it in case the other guy fails. ^.^
Click to expand...
Click to collapse
Nice future-sight on this post

I just tested the file upload in the command-line again with static (coded by hand) filesizes.
Here is a new vid (hahaha famous ultralowres) where a file is upload to a just-formatted kin (CB+power).
File: dstpa.mp4 (BEP- Don't stop the party), 33.1MB
Destination: Kin storage root
Playable after upload: yup!
Mp4 tags: At all .
Just a upload showcase, not just naming the procedure .

nice nice ^.^
more freedom in file management I like.

woot goodjob

I have to give you kudos for your dedication. You kept at it even after you bricked your first kin.
I patiently await a release.

I'm trying to get the alpha release up today (tonight here).
I was in the mood and moved my coding-ass. Solved most of the problems on-the-go, but downloading.
I'm trying to allow multidownload keeping same directories on the pc... just cause i wanted to... rofl.

Hummmmm,
EVERYDAYIAMSHUFFLIN
Mmm after discovering several things, and implementing a lot of bugfixes (didnt know some things about MTP), there it is.
here, and all the versions are updated and uploaded in the 1st post, among the driver for it.
As posted there, i suggest to use it on a virtual machine with .net framework 2.0 cause the removal of the zune's driver for the kin.
You can now take your kin and (if the driver & program behave correctly), upload the files you want to the Kin.
Any type of file, any time.
I'm pretty naughty telling this, but apart from uploading....... i don't check for the file contents... so if any of you want to turn a .exe into .mp4 to look for exploits i wouldnt blame you for testing....
Double naughty if i say that Zune doesnt load info from the files itself, but only what was transfered from MTP (.. poor fella)
You can check that, cause it will only load the filename and name of the mp3, ... cause i did that (before today, i just sent filename, which makes its name blank on zune, like you saw in my video from BEP).
Hope you all enjoy and no errors appear.. rofl.
Btw, there's no donate option, cause i think it's more fair to think about that when the program is known to work, and not just alpha releases .
It's 02:53 AM here, so i better go to bed, to work tomorrow and that things....

I just wish this thing could play games lol.

@Johnkussack
Wow. I have to say thank you for putting your time and effort into really hacking this phone. I can't wait to see someone get android or wp7 running on this thing (if it's even possible with the hack you have, I'm not sure). Ether way, thanks for everything.

[UPDATE 2] The Ultimate HOX ToolBox [UNDER CONSTRUCTION]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------------------------------------- UPDATE 2 -------------------------------------
hey guys this seems to be harder than I thought, but till now I manged to create a solid code to base my work on
and I'm thinking of "HOX-BOX" as a name for my baby, what do you think?
Done since Update 1
- ADDED: dynamic shell (context) menu for faster flashing .. including the choice to enable/disable it
- ADDED: an advanced detection system, far better then the simple "devices" known command, this tool will be able to detect a 100% accurate state of the device including (adb/mtp - mass storage/camera p2p - fastboot - connected with no drivers - current drivers version - the path for the mass storage)
This toke me 2 days of hard work and it's based on the detection of system Drivers/Vendor ID status, so it can't go wrong
- ADDED: advanced model detection command before flashing to prevent wrong flashes
- IMPROVED: Interface and logging
- INCLUDED: HTC Drivers 32 and 64-bit adb/fastboot
- INCLUDED: USBDeview (helps with retrieving HTC's vendor IDs and Product IDs)
- IMPROVED: data size by removing unnecessary platform tools
Still Struggling with
- Live Stats
Normal stats are OK and ready but keeping the CPU stats alive is making the software unstable, I'm still working on this
- Drag n' Drop handlers
- Flashing a ROM through PC
haven't really gave it the time yet, i'll be looking into it as soon as I stabilize other current commands.
------------------------------------- UPDATE 1 -------------------------------------
The Tool Is now under construction
I Finished the following so far
- UI main Menu
- INCLUDED: platform-tools_r16.0.1-windows
- INCLUDED: 7z.exe and 7z.dll (to flash boot.img without user interference)
- One Click Flasher for kernels and recoveries is now ready (CWM, TWRP and BOOT)
- Logging system that creates user-friendly (humand readable) logs and Advanced Log that lists command and their returns
Now Working on
- Live stats about battery and processor
- a 100% PC based flash code you just plug in your HOX, select a ROM , and the tool will transfer it to the SD, flash it in recovery, erase cache and delvik, do selected wipes and flash the boot.img
this is a tricky process but I have all the info I need , and now I'm on it
------------------------------------- OP -------------------------------------
Hey Guys
Lately I've been thinking of Creating a Tool that works with PC to make common tasks easier
I have a good experience in programming/ui/animation/batches
The Tool is basically an AIO TOOLBOX for our One X (for now)
I have some Ideas , but I need some feedback before Starting
it will be User-Friendly.. Noob proof and really well themed
WHAT I HAVE IN MIND
• basic functions
- mode detection
- get device props (CID, Mainver, Current ROM, Free Space, Model and so)
• Includes
- fastboot environment
- latest drivers
- SU flashables
- recovery Images
• Commands
- help connecting your device by installing the drivers automatically, detect the current mode (and enable/disable options based on the mode)
- help with the bootloader unlock
- flash boot.img (even if not extracted) you can just select the ROM zip and the tool will extract the boot and flash it automatically
- flash recoveries
- push (transfer) files using adb (even if stuck in recovery) without writing any code (WYSIWYG), just choose files and click push
WHAT I NEED FROM YOU
(Done!) 1. should I do this? .... does it worth the time, or there is similar tools
2. if you think I should do it, should it have more features (than the mentioned above) , and please name them with details if possible
3. suggest a name for the tool
I have the ability to integrate any fastboot/adb command you can think of into the UI, with a nice animated design
but I can't do miracles such as unlocking the phone without the help of (HTCdev) or S-OFF your device, so please don't request such things

Re: I need your thoughts - The Ultimate HOX ToolBox
1. Definitely you should do it! (although there is toolkit which can unlock bootloader and flash a recovery already) More advanced features would be welcome!
2. A few things:
Maybe fetch a RUU automatically based on main version from
BugsyLawson's server
or
ruu.androidfiles.org and automatically install it.
A tool that fetches a firmware zip based on cid and flashes it.
Adb shell
Boot repacker
3. NoobKit-9000
Sent from my One X

TToivanen said:
1. Definitely you should do it! (although there is toolkit which can unlock bootloader and flash a recovery already) More advanced features would be welcome!
Click to expand...
Click to collapse
Glad you feel this way
TToivanen said:
2. A few things:
Maybe fetch a RUU automatically based on main version from
BugsyLawson's server
or
ruu.androidfiles.org and automatically install it.
A tool that fetches a firmware zip based on cid and flashes it.
Adb shell
Boot repacker
Click to expand...
Click to collapse
- Communicating with servers and downloading is a tricky thing, they would have to work with me for this
if I get enough help from them , I Would deferentially do it.
but at the very least I will include a guide that will tell you the exact name of the RUU/Firmware that needs to be downloaded (maybe even search for it)
- adb shell .... Will Do :good:
- boot Repacker ... I have to do some more reading about this, but I think I can do it :good:
TToivanen said:
3. NoobKit-9000
Click to expand...
Click to collapse
:laugh:

Re: I need your thoughts - The Ultimate HOX ToolBox
Like the idea of a nice clean tool.
I haven't felt the need to root or flash yet, but as there is no s-off yet the process seems slightly more involved than it was for my old Desire, so it is a bit off putting. If there are tools that can help - will use them.
I know that sounds noobish - and it is
Sent from my HTC One X using xda app-developers app

Re: I need your thoughts - The Ultimate HOX ToolBox
One click kernel flasher would be nice lol
A
Htc One X Viper 3.4.2

Re: I need your thoughts - The Ultimate HOX ToolBox
There's always one click flash tools they do a lot of what u said flashing, a useful tool would be to indicate where memory is used these devices are limited on memory biggest downfall on htcs part Imo
Sent from my HTC One X using xda premium

Hey mate,
Do it !! Competition is good, Hasoon already has a toolkit but as mentioned choice is brilliant ! So get on it and goodluck, can't wait to see your final program .
PS - Check your banner image !! You missed the "U". It is "Your ltimate tool flasher".

Wilks3y said:
Hey mate,
Do it !! Competition is good, Hasoon already has a toolkit but as mentioned choice is brilliant ! So get on it and goodluck, can't wait to see your final program .
Click to expand...
Click to collapse
Thank You!
and Yes I do like clean Competition , and giving people choices.
Wilks3y said:
PS - Check your banner image !! You missed the "U". It is "Your ltimate tool flasher".
Click to expand...
Click to collapse
OOPS!

-"Live stats" would be great, showing instant info about cpu cores in use and freq, battery % and mA flow, ram usage, live logcat + kmesg, gpu freq...
-A good file explorer that allows to edit files "on the fly"
What do you think? want more ideas?

Juanig said:
-"Live stats" would be great, showing instant info about cpu cores in use and freq, battery % and mA flow, ram usage, live logcat + kmesg, gpu freq...
-A good file explorer that allows to edit files "on the fly"
Click to expand...
Click to collapse
I Will definitely Try to include every feature I can with time
I have a lot of reading to do, but if it is possible then I'll do it, even if not in the first release, I WILL try to include everything as future versions build up
Juanig said:
What do you think? want more ideas?
Click to expand...
Click to collapse
Thank you, and if you have any other useful ideas, why not

Re: I need your thoughts - The Ultimate HOX ToolBox
Great idea, I initially used a toolkit when first flashing mine but it's nice to know what your actually doing to your phone and I have since learnt all the commands. So my request is to somehow show the user what your automating so they understand what's going on with their phone. Maybe like a log/command type window that can be shown or hidden for those that want to see what's happening.
Cheers
Sent from my HTC One X

Re: I need your thoughts - The Ultimate HOX ToolBox
Yes agree with herbie u wanted to use a toolkit but would have also benefitted from knowing the commands as something went wrong during the flash with the tool kit
Htc One X Viper 3.4.2

Re: I need your thoughts - The Ultimate HOX ToolBox
Great idea
Thank you, I must have this in my tool
Sent from my HTC One X

ADDED UPDATE 1 TO THE OP
a beta release should be available soon :fingers-crossed:

Maher88 said:
ADDED UPDATE 1 TO THE OP
a beta release should be available soon :fingers-crossed:
Click to expand...
Click to collapse
cant wait!

[TOOL][Windows/Theming] BatchAPKTool

As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release

Cool.
Suggested it for the portal.

Awesome - thanks a lot!
A slightly updated version is coming sometime soon.

New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.

dfkt_ said:
New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.
Click to expand...
Click to collapse
Not really into cooking ROMs these days, but this tool will definately help if I enter the kitchen again and try my hand at themimg.
Thanks a lot :good:

Thanks for this, it's really productive

Thanks for this tool, Really useful & helpful!

Thanks bro, it makes so much things easier

Thanks mate. I'll give a try asap
I saw your thread from the portal and this is worth cuz it looks very useful on paper :good:

Glad you guys find it useful.
Don't hesitate to report eventual bugs, or illogical combinations of options, etc.

dfkt_ said:
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not.
Click to expand...
Click to collapse
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page

dfkt_ said:
As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release
Click to expand...
Click to collapse
Now this will come in handy very very much! Keep up the good work and keep adding features to it
Sent from my Galaxy Nexus using Tapatalk 4

Not sure that your quote is useful.

8notime said:
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page
Click to expand...
Click to collapse
Yeah, that's a dilemma - the URL for the JRE direct download link is dynamic (the "1880261" part), changes with each new version. So the script would have to be constantly updated (or some really sophisticated URL crawler implemented). The lazy-but-safe way of linking to the index page is probably the best I can offer. Or maybe it's safe to link to the root JDK/JRE download page (which seems to have a fixed URL), and tell people that the JRE is enough, no need to get the JDK.

THANK YOU
Great tool. Im currently working on my dialpad theme. Great find! :good:

[ROM][UNOFFICIAL][R/A11][F500,LS991,H81x,US991,VS986] /e/ OS | BYE Google, HELLO Privacy!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
****
These builds are for all G4 models: official unlocked and UsU'd devices
****
UsU? http://bit.do/unlockg4​
About /e/​/e/ is a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features​
Based on LineageOS so a very stable base
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?​
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed but NOT activated by default (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore allowing in-app-purchase on microG
added Lawnchair (latest from their TG group)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules /e/ defined.
Known issues​Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
Check the current issues at the github tracker (feel free to help, provide logs etc!)
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Requirements​
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
... and NO SUPPORT for the BETA v29A as well!!
-> for your convenience I have created TWRP flashable files for that !!!! (click)
Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
in particular that means this thread is for:
F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
Latest TWRP - PREVIEW build: click or SHRP build: click
Do a full Nandroid backup before doing anything!
Installation​
This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N will not work)
Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download​
Not available (yet) -> OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install):
http://leech.binbash.rocks:8008/e-os/a11
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my CUSTOM builds have OTA support like OFFICIAL has!)
Note:
CUSTOM builds: Builds are updated as soon as possible. There is no fix build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs​
CUSTOM: posted in my Telegram build channel
OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
Support​Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits​
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The LG G Four team (aoleary, steadfasterX, Paul Tully)
and more..
Sources
build manifest
e OS source

Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: LIMITED SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have magisk installed currently UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Try to re-produce the issue. If it is gone, its magisk related. otherwise follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and is placed very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: set magisk to core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch Factory Reset and let it do its job
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
yes this might happen when the following has been solved / implemented (which is NOT the case currently (see known issues):
- selinux = enforcing
- device encryption working
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log (requires a linux system):
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt
Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
Q #07b: How can I provide a clean boot log?
Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
So here you go for a much easier way:
boot Android
once booted : reboot to TWRP/SHRP
when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
open a terminal on your PC and type:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/
Q #8: upgrade your bootloader stack only?! Read here how:
Check the OP of this thread which has TWRP flashable files linked.
Q #9: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #10: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #11: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #12: I have graphic glitches / issues, what can I do?
My builds using OpenGL instead of skiaGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
Is there any fix for skiaGL coming? No, details here .
To check if your current ROM version is using skiaGL do this:
Code:
adb shell getprop debug.hwui.renderer
If you get an empty result or "skiagl" it means skiaGL is active.
If for any reason you wanna enforce skiaGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer skiagl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=skiagl" >> /system/build.prop
sync
reboot
.-

I uploaded it, good speed, I will continue to try. Thank you

Thanks for this new ROM
I recommend a full cleanup with format
The only issue I have so far is that I can't connect to my Murena.io account, it keeps on loading. Logs attached

Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.

cvmg333 said:
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
Click to expand...
Click to collapse
The blackout when phone display is off is a well known issue since years with any custom ROM for the g4. We tried to fix that for a long time without any real success.

Interesting note, i did not know about it, thanks for the tip, i will use light theme now onwards then, got another little problem with the microphone, the other person hear me to low, only when i use speakerphone in a whatsapp call, with out the speakerphone activated every thing is working well, have not tried in a normal telephone call yet, i have tried changing microphone volume setting in kernel with ex kernel manager, but no success in that, changing screen colors and saturation works in that app, thank you.

@steadfasterX this could be tried https://github.com/sthomsonpl/devic...mmit/07db7d8be41997765f9a0c60d7e7476b5440545e

I installed this ROM yesterday, and its running fine so far.
Thanks a lot for bringing this gem to ye ole G4.
You really did an excellent job!

Auto rotate not working. H815 UsU'd. Yes - flashed UsU zip.
Edit: Also, when turning on bluetooth, connecting bluetooth headphones then playing a video, bluetooth turns off.
I haven't tested bluetooth on the pie /e/OS or the various LineageOS builds, so it could very well be affecting those too.

Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?

pizza_alarm said:
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
Click to expand...
Click to collapse
flash 20p bootloader stack and modem

Thanks. Where can I find the correct bootloader and modem files?

pizza_alarm said:
Thanks. Where can I find the correct bootloader and modem files?
Click to expand...
Click to collapse
pls check the OP -> Requirements (bootloader stack), Installation (Modem)