Database Users

Big Request!

Can someone pleeeeease, pretty pleaeeeease, create the speedo battery gauge for the Stock Rom?

lion766 said:
Can someone pleeeeease, pretty pleaeeeease, create the speedo battery gauge for the Stock Rom?
Click to expand...
Click to collapse
On a stock ROM with s=on it's impossible

Hello Neidlinger!
I am showing S-Off. I guess, maybe I am describing it wrong. It is the Sense UI, Stock?

lion766 said:
Hello Neidlinger!
I am showing S-Off. I guess, maybe I am describing it wrong. It is the Sense UI, Stock?
Click to expand...
Click to collapse
Since your phone is s=off it is doable, because you can change the /system folder and have stuff stick. With that being said i know there is a thread in the development section that has a lot of gauge options on it. If i can find it i'll post a link to it for you.
edit
===================================================
http://forum.xda-developers.com/showthread.php?t=852013
i have no clue what is in that thread, as far a meters go but that is the one.

{
"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"
}
Thanks for the work on the link Neid. I am actually using one of those now.
I was specifically looking for one like the link above displays. Apparently I haven't been able to find that exactly.

I know some of the custom roms have it available, but was curious if there was a file or something that could be pulled from them to make it available for the sense, stock ui

I know one of you stud guru's can do this in like 5 minutes!

http://forum.xda-developers.com/showthread.php?t=990829
Cook it up here if you want. There is an icon like it in the battery mods section.

damn that's tough, I can't find the needed files. Thank you for the link however

how did you theme your current setup? If you used a flashable zip, you use that. If you used the t-mobile theme engine you use the apk. It shouldn't be tough. With that kitchen you just need something to start with, so as long as you aren't running straight stock no theme, it's a quick file dump and let the kitchen cook it up.

I am using the recovery back to stock, which was titled, 1980-01-06.00.08.33. I got it from these forums for a stock recovery with sense.
I am still rooted, and S-off, verified through 3 sources, and i can add mods.
I tried looking in that file last night, but didn't see anything.
You are saying just throw that entire zip in kitchen? I will try that tonight (Can't remember if the zip was over the 9mb limit kitchen had, which I think it was)

no that won't work. You need an apk to get it going, since you're using stock you'll have to find one of the t-mobile theme engine apks already included with stock. I think androidian is one of them. I'm a little surprised, for someone who wants a really customized look you shouldn't be using an odexed ROM. Something like RoyalGlacier would be so much better. It's MySense, stripped, deodexed, zipaligned, and has a lot of tweaks that are great. Much better kernel included as well. Take a look at the thread in the development section. The touchpanel update included in faux's kernel is worth it by itself, it's like getting a whole new phone.

Ahh Darinmc, thank you for taking the time to reply.
I actually have RG ready to flash on my SD, just hadn't yet. I know RC2 was giving me a force close loop, so I undid back to stock until they had more time to work bugs.
I think I will give RG a shot.
Again, thank you very much for replying, think I will try Androidian and then RG

The best thing about TR ROMs is their support. Follow their instructions for installation to the letter. After that, if anything, and I mean anything, goes wrong, post a detailed report in the thread and they will bend over backwards to get you up and running. Having problems with RC2 probably had something to do with a bad install (this is not pointing the finger, simply pointing out that when dealing with custom ROMs many things can happen during an install), the TR instructions are more detailed and generally create better results. Happy flashing!

[ATTN ROM COOKS/NOOBs][READ BEFORE FLASHING] Please prompt users to create backups!

Dear newbies, please back your device up before updating, trying custom ROMs, Kernels and other modifications. Most common and easy backup methods can be found here. Please note that Acer has released firmwares that broke the update cycle. First thing to do when getting a device is a backup or you might get stuck on an old version!
Dear ROM cooks, please prompt users to create backups. Although for some it may seem common sense, other may suppose that restoring their tablet is an easy task - until Acer releases an OTA update to the current 3.1 we can't say for sure our stock 3.1 will match all the required checksums.
Please do not modify Device Information, Model number, Android version, SN and SNID if possible. I understand you take pride in your work, and you should but by over-branding the FW you can be making it very hard for developers to properly identify the device and address bugs. Some will even ignore reports from modded devices.
Thank you for your cooperation.

I agree flashing custom roms can brick a phone or tablet. Users should be aware of tue possible consequences, but they rooted the phone which makes all this possible. That by itself largely takes them outside of support.
I agree blanking sn and snid, as well as change device types etc should be pointed out where possible, but being realistic most devs will not devote the time for it.
I personally do not develop on android, but have dealt with custom roms on multiple android and other os's. I generally make I have a way to return to stable state. The net result is i have never permanately bricked a phone. Close a few times.
I think a good mandatory read post about the dangers of rooting, installing root apps or flashing romss and kernels, would a good idea before people can accesss the sub-furoms devote to that stuff.
But realize that most owners of any android, iphone, windows mobile, etc will never root(jailbreak). Only the curious. Rememberthe saying about curiousity and the cat.
DEVs - Keep up the good work.
Users - Understand the risks. If you don't understand what you are doing. THINK THREE TIMES
Hopefully, if something goes wrong someone here can help.

FLEX Version : Blank
Product SKU : 3G
SN : Blank
SNID : Blank
My Flex Version : 22_COM_GEN1 (was 04_COM_GEN1 but on my second tablet now it's 22_COM_GEN1)
My SKU should be WIFI
My SNID Should be XEH6LAN00511515CF11500
My SN Should be 11508932915
MY UID :0x03807001422172d7
How put those information back to the tablet????
rooted for sure, root explorer indeed... but where, how, etc... thanks if someone know
How to get back those lost information:
Serial Number ID (SNID)
go to https://registration.acer.com/myaccount/page11.do?link=kln2s.redirect&changedAlts=
and login
then get back your SNID from your devices list your register at ACER.... you did it didn't you ?
or that is not a SURE thing, but on my bills I have the Snid wrote down.
Serial Number (SN)
{
"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"
}
Flex Version
(that is related to the firmware, it's the last group starting with a number)
22_COM_GEN1 for the 4.010.22_COM_GEN1
SKU
WIFI

Tell that to the people trying to fix their tablet after flashing your ROM.
Just asking nicely to post a note about backing up, but no, you just have to be a jerk.

Thanks for sharing, hopefully people read it before flashing.
This is just an effort to caution the noobs and request the ROM chefs to caution the noobs, we are not trying to blame it on the Chefs, and if developers feel that noobs won't read this - well we can't force anyone to read this - but we can try and help them to not brick their device - which will lead to another 100 threads with the title " I brick my device - whats to dos now " in the dev section, if by one thread we can save 100 new threads - maybe worth a shot.

Just a suggestion - Regarding the ROMs

With the Notes Development section being maintained properly, I was thinking if we can create a sticky in the Development section listing all the available roms and list of there unique feature, if they are based on stock rom or others (this will reduce the chance of people flashing stock rom and bricking there phone)...
This will help people chose the ROMs more easily..
Again this is Just a suggestion:angel:.

ravi_buz said:
With the Notes Development section being maintained properly, I was thinking if we can create a sticky in the Development section listing all the available roms and list of there unique feature, if they are based on stock rom or others (this will reduce the chance of people flashing stock rom and bricking there phone)...
This will help people chose the ROMs more easily..
Again this is Just a suggestion:angel:.
Click to expand...
Click to collapse
+1

Good idea... I does sometimes get tricky keeping track of all the ROMs available, and also if they are safe, with regards to the brick bug thing...
+1 to the idea...

Best place wood be the Wiki,
see the list of ROMS there.
Could add structured informations in a table with useful columns (like last version with date, used Kernel (and so Brick risk), Android base etc.).

chintamanijaipuri said:
+1
Click to expand...
Click to collapse
:good: I too expecting similar kind of list

ThaiDai said:
Best place wood be the Wiki,
see the list of ROMS there.
Could add structured informations in a table with useful columns (like last version with date, used Kernel (and so Brick risk), Android base etc.).
Click to expand...
Click to collapse
Wiki is a good place, but it does not provide a quick comparison of all the roms that are available. Everyday a new rom is popping up :laugh:. So for a user to pick a ROM we can provide a review sort of a thing like.
Rom : Paranoid
Base:CM09
Flash Method: "Link". Flash over stock GB.
Feature: Hybrid,Tablet and Phone mode. CM09 Base.
Bug:Link to bug list.
etc etc.

+1 for a comparison table
It would also be interesting that the information displayed whether or not particular hardware features were functioning or not. For example does the S-Pen work, GPS work, camera etc.....

I suggest this some time ago but no one had the time to keep it up (I no I dont..don't even have the time to keep up the torrent thread like I would like to)
The problem is it can be alot of work to maintain and up to date thread but if someone wanted to take it on I would be all for it

Would this help? I just tried to make a table with some informations that might be necessary. If you like this I will change the wiki page and add the details in the evening (and will try to maintain it).
{
"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"
}

+1 for ThaiDai table, at-least this will be simple to maintain.

I started such Thread here in General Section...it just went unnoticed...lol

ThaiDai said:
Would this help? I just tried to make a table with some informations that might be necessary. If you like this I will change the wiki page and add the details in the evening.
Click to expand...
Click to collapse
That looks neat and precise, can you also add a column for feature and the link to thread and flash base like if it should be installed over GB or ICS.

ravi_buz said:
That looks neat and precise, can you also add a column for feature and the link to thread and flash base like if it should be installed over GB or ICS.
Click to expand...
Click to collapse
The link is included in the first column. But I do not understand the two other columns:
feature?
flash base?
Can you give an example for this. Thanks

ThaiDai said:
The link is included in the first column. But I do not understand the two other columns:
feature?
flash base?
Can you give an example for this. Thanks
Click to expand...
Click to collapse
Features = We can tell some unique feature of the ROM, like for Paranoid we can say its a hybrid rom. For Clean Note we can say thats its stock based and optimized for speed.
Flash Base: Flash it over GB or Flash it over ICS.

Features: too much text for one column would result in unreadable table, dangerous, but will try.
Flash Base: there are too much ways to install, and with the type column GB or ICS or CM or... is obvious

AOSP port to Note-4 trltexx,trltedt

Greeting Developers ,
I am new to this ROM building/porting process.
I want to install Vanilla Android on my note-4, so after questioning Google number of times, I came across official Android development guide on official Android website: https://source.android.com/source/downloading.html
I have downloaded the Android source locally and was following various Guides and tutorials from XDA-University & forums only for the development process. http://xda-university.com/as-a-devel...ng-source-code
I discovered that for downloading/configuring the build for a specific device(trltexx), we need to create a localmanifest file that contains device tree, vendor and kernel configuration links for repo syncing.
Now, I want your expertise to guide me forward from this point. Questions being:
1. Can I use CM or other projects (eg. AICP etc.) device configurations for this AOSP project.
2. Can I use these configurations for cross-version android build, say if I want to compile version 6.x, can 5.x configs can be used. (Manufacturer will take several months to release version update)
or Create new configurations using some guide/tutorial/book or something.
In XDA, I know I'm at the write place posting my questions and asking for expertised help.
Thanks!!

Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe

contramundi said:
Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe
Click to expand...
Click to collapse
Thanks for your reply @contramundi, I got N-910G which is a snapdragon version. I just want to know if I can use AOSP sources from google and device configurations from CM, AOSP rom can be built or I need to use specific device configurations for AOSP.

Why?
There's no need to start a whole thread for this as there are numerous threads to ask such a simple question. You didn't say which version of AOSP you were building, but regardless-- yes, you can try to start with CM device trees, but prepared to change quite a bit as there are quite a few dependencies on CM enhancements there.
If you want a truly "vanilla" experience, I"d use the Code Aurora sources, not AOSP's, as CA has all the latest Qualcomm support/bug fixes for MSM and APQ devices, which only may hit the AOSP tree when they do a new release. It is the repository where Samsung starts with their version of Android, and it's where CM also gets its qcom support/repositories.
Gekke, slahyer, and I have done the work to make the Note 4 build/work-- both for lollipop and now starting for 6.0 Marshmallow. And speaking of 6.0, before you even think of building that w/AOSP, you'd also need tons of patches for the Samsung kernel which I also have also already done.
Rather than just applying our work to vanilla AOSP though, you're welcome to join the community effort on CM 13, which has already been successfully built for tmo, eur/xx, spr, and edge so far) on the other thread. You'll need to read about the last two months of posts to catch up. I also posted a link to instructions on building CM-13 in my .sig below.
If you are insisting on straight AOSP by yourself, I would recommend you look at the shamu (Nexus 6) model. It is the same soc as the Note 4, albeit with different peripherals (screen, fingerprint reader, etc.). But it might be a place to start. My build instructions would need some slight tweaking for vanilla AOSP, but I'm sure you could figure it out.
ft

Compiling 8.1 oreo for note 4
Hi,I have been trying to compile aosp for note 4 snapdragon variant.I have downloaded the repo and the required files.I started the compilation and after 25% of the compilation is over,it shows some error and stops the process.Can anyone please help me.I have added the screenshots for reference.
{
"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"
}

LineageOS 18.1 for X00TD - Anyone using it?

Hi all,
I've searched and haven't found anything related with Official LineageOS 18.1 on Max Pro M1 (X00TD) and because of that, I'm asking kindly if anyone here is using the LineageOs version.
What are the issues you've found so far?
Kind regards,
Carlos

There are some who use it, yes, including me:
{
"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"
}
https://stats.lineageos.org/model/X00TD
And no problems so far. Well, except for some minor things that plague any LOS/Android.
Oh, some time ago I couldnt hear people on the phone: It was just blacking out now and then, sometimes even for a minute... but turned out that the carrier was to be blamed (since other people, even with dumb phones, reported that, too).
PS: If you are missing a thread proper for official LOS18.1 X00TD, yes, me, too! Perhaps we should start our own thread

Thank you so much, @SigmundDroid.
What a relief... I'm not the only one who misses an "official" LOS 18.1 specific thread for X00TD
Since you are already on LOS 18.1, can you please help me with these questions:
- What was the recovery you used?
- Did you root the device?
- What about bluetooth and dual SIM?
(I don't need it rooted anymore and I think some apps, like banking/payments, might not work on rooted devices...)
Again, thanks for sharing your feedback.
PS: I still consider LineageOS the only viable alternative to the stock ROM (since the first Cyanogen editions).
Kind regards,
Carlos

Hola Carlos,
carval2k said:
not the only one who misses an "official" LOS 18.1 specific thread
Click to expand...
Click to collapse
I am actually quite happy someone else asked that, too. In the ROM thread are so many, many, many things but THE REAL MCCOY is missing.
At first I thought it's me but no, it's not me, it's not you, it's them
carval2k said:
- What was the recovery you used?
- Did you root the device?
- What about bluetooth and dual SIM?
Click to expand...
Click to collapse
Had TWRP at the beginning but this year I tried the LOS recovery. It worked and I was too lazy to get back to TWRP again. However, was always nice and easy in TWRP to do backups, I miss that a lot... so at LOS19 I might change back (if LOS recovery does not improve there).
Yes, I did root. Don't need money things and won't do it because I consider phones inherently unsafe.
Fun fact regarding banking: EU's PSD2 demands different channels for safe payments, seems rather stupid to me to have both "safe" channels on the same single device. Sounds to me like an accident waiting to happen.
And just for AdAway alone, I would root again.
Bluetooth: Hmm, no hassle here - headphones work, our BT-thermostat works, sending files works. Did I miss one?
Dual SIM: Yes, does work nicely. Except that it can be a pain to keep things separated - just switched the main SIM but far too often, I still send SMS with the wrong number (and pay per message instead of using other card's flat) but that blame is on me, I guess
Oh, and one more thing: I also don't use GApps (Google IS evil) and get along fine with fdroid/aurora. Some stupid apps insist on google's framework like ebay but that's not worth it to have the entire barrage of google's spyware, eh?
carval2k said:
consider LineageOS the only viable alternative
Click to expand...
Click to collapse
Same here

Oh, forgot one thing regarding rooting:
magisk requires patching... and with every single update (or perhaps I am doing it wrong). That can be quite the pain.

Hello, I'm using LOS 18.1 (official), everything works for me except NFC, everything worked on the drain.

Hey! Using 18.1 here too, very impressed so far. Everything seems to be working well, I passed SafetyNet too, so I shouldn't run into any problems. I just wish I could remove that pesky "Unlocked bootloader" warning at the beginning.

ayuinaba said:
Hey! Using 18.1 here too, very impressed so far. Everything seems to be working well, I passed SafetyNet too, so I shouldn't run into any problems. I just wish I could remove that pesky "Unlocked bootloader" warning at the beginning.
Click to expand...
Click to collapse
Got ahead of myself --- found a bug with the screen recorder. It seems the microphone volume is very very quiet compared to the device volume. If I'm only using the microphone, it works fine. Not sure what this is about. Will be checking this out more thoroughly.