yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] tungdil:
Additional Information

Hello TK-Glitch,

it's me again ;)

I did some further "research" in my secondary "L- ROMs" (the one I created for providing the information above and the one that does have SuperSU 2.23 installed and has root). I had a more detailed look on the boot images. In both cases your kernel is installed. I pulled the boot images using adb and unpacked them using unpackbootimg and then also unpacked the ramdisk. Binary the two images are not identical since the Glitch kernel configuration was slightly different:

console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=1 vdd_uv=1 max_oc0=1728000 max_oc1=1728000 max_oc2=1728000 max_oc3=1728000 min_clock=384000 abc

v.s.

console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=3 vdd_uv=3 max_oc0=1890000 max_oc1=1890000 max_oc2=1890000 max_oc3=1890000 min_clock=162000 abc

but I could not see any difference in the RAMdisk and the other main components dspite the fact that SuperSU 2.19 was used in one case and 2.23 in the other.

[EDIT] After reading TK-Glitch's next Post I realized that I made a mitsake and picked a wrong boot image when trying to compare so the following is wrong:

Tassadar's boot image is, of course, very different. One thing that I saw (because I remembered that SuperSU 2.23 "...fixes a number of SELinux policy issues...") is the difference in selinux-version. In Tassadar's image I find:

Android/aosp_flo/flo:5.0/LRX21M/scott11042320:userdebug/test-key

while your selinux_version says:

google/razor/flo:5.0/LRX21P/1570855:user/dev-keys

[/EDIT]

Maybe I am wrong but I think my problem was caused by the combination of Tassadar's build of the ROM and the Glitch kernel and, I was just lucky that the latest Beta of SuperSU helped curing it.

Best regards,

tungdil
[Nexus 7 (2013) Q&A] nokiagye:
Latest glitch and lollipop stock

I can't unlock many times the screen I have enable the swipe options
[Nexus 7 (2013) Q&A] Tk-Glitch:
[MENTION=5098312]tungdil[/MENTION]

Thank you for your patience and researches tungdil !

The files SuperSU 2.23 would modify are most likely init.rc and sepolicy I guess. These are the two only files Glitch is potentially patching in the extracted ramdisk(from the current boot.img) when using root settings (fstab.flo is for F2FS partition mounting). Glitch doesn't come with its own ramdisk to enhance compatibility and will instead extract the current one, patch it with the options you've selected then repack it with the Glitch zImage in a new boot.img that'll be flashed at the end of the Aroma installer script. The selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.

I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary. I may be right in thinking they're not the same when I'm looking at your selinux_version files content if you didn't switch kernels. You know what you did anyway.

It could indeed very well be something in Tassadar's build or some ramdisk changes he made breaking my patches. I didn't test his rom thinking that after an AOSP built rom and the official Google image were both getting root for me after applying Glitch it would work for every other AOSP based Lollipop roms. I may have been wrong.

I'll check Tassadar's build and search for a fix. Thanks again tungdil !
[Nexus 7 (2013) Q&A] tungdil:
Hi again, Tk-Glitch!

Thanks for your comments! I appreciate having the chance to learn something.

Oh, I see! I should have had a closer look at your flashable zip. After doing so, and looking into what "I found" I had to realize I made a mistake in picking the wrong boot image for the analysis (I have multiple secondary ROM's installed) :o In fact the selinux_version is, of course, the same (google/razor/flo:5.0/LRX21P/1570855:user/dev-keys) before and after flashing Glitch kernel.

They should be the same (as mentioned forget about selinux-version :o I guess it was just too late yesterday night).

I tried to explain how I installed the ROM in my first post: "... For both cases [secondary and primary ROM] I used Tassadar's build. For the latter [primary] I copied the installed secondary ROM to the primary slot [using TWRP] ...".

If there is anything else I could do to help let me know! I'd be more than happy.

Best regards,

tungdil
[Nexus 7 (2013) Q&A] Tk-Glitch:
[MENTION=5098312]tungdil[/MENTION]

I can understand better now, thanks for the confirmation.

My english is pretty limited to be honest so I may be understanding things wrong sometimes. I can also feel that I'm not able to express fully what I'd like to from time to time. It can be another limiting factor in some cases where my explanations or questions could be unclear for someone speaking better than I am.

I didn't find the time yet to check for Tassadar's build so I'm not in need for more for now. I'll get back to you as soon as I've made some progress on the matter - even if it's just to keep you informed - as it could also help someone else.

Thank you for your support and dedication.

Have a nice day tungdil :)
[Nexus 7 (2013) Q&A] pogo_01:
W.O.W

Thank you for this kernel!! It turns my adreno 320 to adreno 330 :)
[Nexus 7 (2013) Q&A] pranauk:
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
[Nexus 7 (2013) Q&A] pk-sanja:
Hey [MENTION=3847629]Tk-Glitch[/MENTION],

First of all i want to say thank you for this wonderful Kernel :).

I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.

The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.

I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.

Thank you in advance :).
[Nexus 7 (2013) Q&A] Tk-Glitch:
Strange to say the least since you didn't have issues previsouly. I've seen ghost touches on a friend's N7 and the only true fix was unplugging and replugging the display cable on the motherboard. BTW, ghost touches are almost always linked to the bad manufacturing of the N7.

I don't have any myself, on both r306 and r307, but my tab was never affected.

My battery is lasting much longer since Lollipop, so you may want to check for wakelocks.

These days I'm using 1.7GHz CPU, 600MHz GPU, -75mV on each CPU step, -100mV on each GPU step, ondemand governor, Glitchy L2/cache OC, and S2W/DT2W disabled.

Hope it helps !
[Nexus 7 (2013) Q&A] pk-sanja:
[MENTION=3847629]Tk-Glitch[/MENTION]

Thank you for your answer Tk-Glitch, i will check the wakelocks.

And thank you for sharing your setup,

i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
[Nexus 7 (2013) Q&A] Tk-Glitch:
Of course mate.

My CPU needs 1.025V for 1.7GHz (PVS 3). For the GPU, I did make the GPU undervolting selectable (for all steps at once) in Aroma. You can tweak the values in the glitch script (init.d) if needed.
[Nexus 7 (2013) Q&A] pk-sanja:
[MENTION=3847629]Tk-Glitch[/MENTION]

I see very nice :), mine does 1050mV in 1,7Ghz not much differenc. Ups my mistake i thought the GPU undervolting in Aroma Installer is behaving like the CPU undervolting, only for the lowest Frequenz.

Thank you very much for you time, at home i will do a full factory reset and flash your kernel of top with the settings.

Have a nice day Tk-Glitch.
[Nexus 7 (2013) Q&A] Tk-Glitch:
[MENTION=5345451]pk-sanja[/MENTION]

My pleasure.

Have a nice day as well pk-sanja :)
[Nexus 7 (2013) Q&A] pk-sanja:
Last Question :D, i'm at home and would like to know which Rom are you using?
[Nexus 7 (2013) Q&A] Tk-Glitch:
I'm running latest GROGG88's AOSP 5.0.2 rom as main rom :)
[Nexus 7 (2013) Q&A] rudeex:
Issue with Otg y and USB audio dac

Hi, i,'m using your kernel with cm12 but I have an issue with the recognition of my USB audio DAC after the tablet lose power.

I have fixed my nexus 7 in a car enviroment and I cannot plug and unplug the otg cable in order to make the USB audio start or reboot always the device, because in these way (rebooting or plug and un plug) it work but I can't do this in my car.

I think there's an issue in USB host mode management that don't recognize the USB device when lose power andò after return. It's a kernel bug or another limitation? Thank you.
[Nexus 7 (2013) Q&A] Christian Collosi:
Amazing Kernel

Just tried out this kernel and it's pretty amazing, thank you for your hard work!
[Nexus 7 (2013) Q&A] Tk-Glitch:
Sorry for the delay, I didn't see your message earlier. The Nexus 7 2013 is pretty bad for a car installation compared to the 2012 model. The hardware in itself is a limitation on this tab. Nobody figured it out at the moment as far as I know. It may not even be possible to fix this.
[Nexus 7 (2013) Q&A] tungdil:
won't boot AICP nightly

Hello!

Not sure if I should ask the question here or in the ROM's Q&A thread?

This is the situation:

flashed aicp_flo_lp-9.0-NIGHTLY-20150424.zip as secondary ROM in MultiROM

let it reboot for finishing the installation and did NOT install anything

flashed Glitch-N7-r330-CM-restore.zip

reboot gets stuck at the Google logo (when starting the ROM) and will reboot after some 10 seconds

Notes:

didn't have this problem before 5.1

it does NOT occur with CM-12.1

all other secondary ROMs are still working

reflashing AIPC's kernel would solve the boot problem

also tried Glitch-N7-r330-CM-full.zip, Glitch-N7-r330-restore.zip (I know this is stupid), and r327; with the same result

When showing the Google logo the N7 is not accessible via adb. Any ideas what else I could do or check?
[Nexus 7 (2013) Q&A] Tk-Glitch:
[MENTION=5098312]tungdil[/MENTION]

I'm STILL trying to find out what's the problem here, with no success so far. I was able to get a stable Google logo (not looping), but nothing more. This is the only rom I have tested that is having this issue though, but I'll continue to review AICP sources and hopefully find a way to fix it.

I'm a bit discouraged but not yet defeated.
[Nexus 7 (2013) Q&A] tungdil:
Thanks a lot for having a detailed look! I wish I could help somehow. I did some really stupid tests. Don't think this helps but still wanted to let you know about some results...

Situation: I am using MultiROM; AICP Nightly of May 02 (as I know this is working fine) as secondary ROM; AICP freshly installed, booted once, no APPS or any configuration changes; modifications to the ROM made using my Linux-PC and adb shell -- just by copying the boot.img into the corresponding directory on the device.

1. Test: Exchanged the kernel from your boot.img with the kernel from AICP. This was done using abootimg -u ... on Ubuntu. With this modified boot.img the system boots but it takes a while.

2. Test: Exchanged the kernel from AICP boot.img with your kernel. With this img system does not boot and will loop after showing the Google logo.

3. Test: Exchanged the kernel from your boot.img with a CM12 kernel (for details see attached screen shot). The system boots as it should and work as usual.
[Nexus 7 (2013) Q&A] echoot:
Hey glitch! Intellidemand governor is missing with latest kernel. Can you look for it? Thanks! ?
[Nexus 7 (2013) Q&A] Tk-Glitch:
Found. Fixed in next release.
[Nexus 7 (2013) Q&A] anson7329:
I just bought nexus 7 last week and flash your r344-CM kernel.

It is a awesome kernel. Thank you Tk-Glitch !!

I have a question about the cool feature: gpu undervolt.

I set -150mv in Aroma. It still working.

Then I tried change script in init.d folder:

600000\n600000\n600000\n (set maybe lowest volt)

after reboot, it is still working fine.

check /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels_GPU

it show

600000

600000

600000

It seems like set properly.

Is there something wrong with my setting?

Hope it can work for maximum power saving.

Thanks.
[Nexus 7 (2013) Q&A] RidgeTM:
Extremely Slow Boot?

Hello,

Im running this ROM: http://xdaforums.com/nexus-7-2013/development/rom-xenonhd-5-0-2-beta-2-04-01-15-truly-t2993427

I've tried several times now, first with balanced a crossed the board and then stock everything. When I reboot after installing the boot animation is extremely slow and then it optimizes my app all the while being super slow. Once it's finished with that the entire tablet is slow, 5+ second lag on any touch command. I'm not sure what to do from here...

On top of the slowness the colors look off as well, distorted, etc.

I downloaded and installed this. Zip: Glitch-N7-r344-full.zip and also tried the Glitch-N7-r330-full.zip

I hope someone can assist me with this, thank you.

Edit: I think I may have found the issue, the ROM I flashed is advertised as being AOSP but uses a CM kernel, downloaded r330CM Full and am waiting to see if it'll actually boot, fingers crossed...

Edit: Alright everything booted up and has been working just fine, I'll guess next time I'll have to search the ROM thread to see what kernels are compatible...
[Nexus 7 (2013) Q&A] freddienuxx:
When flash latest 344cm over blisspop I lose data! I tried a boot permissive mod from beanstalk /deb! No dice. Is there a fix Thx in advance

Sent from my Nexus 7
[Sprint Samsung Galaxy Note 3] sansari123:
I know about logcat, but fit seems to be a shell command, and it does not seem to be working when I am in recovery mode. I also know the recovery.log. But I still like to see what is happening in real time with my own two eyes. Is there some way of activating logcat while you are in recovery? It seems like I can shell into my device. I get this error

/sbin/sh: exec: line 1: logcat: not found

when I try to issue

./adb logcat

command. I created an image with Android Kitchen which seems to be installed waaaay too fast. i.e. I get a successful confirmation from TWRP, but when I try to reboot the device I get an error stating that there is no OS installed.
[Sprint Samsung Galaxy Note 3] jimzweb1:
I may be way off, but you tried Galaxy Tool by idone. Here is the link http://xdaforums.com/note-3-sprint/themes-apps/app-one-click-hotspot-enabler-menus-t2816159 it has the ability to access logcats and sys dumps, might be worth a try ?
[Sprint Samsung Galaxy Note 3] sansari123:
Hey thanks. I'll have a look at it. I got some stuff with ./adb logcat. I had to reinitialize the tool a few times but TWRP is worth it's weight in gold. I have not had the opportunity to try some of the other recoveries out there. But that is because TWRP does all the things I need to do.
[Sprint Samsung Galaxy Note 3] jimzweb1:
No problem, I have used both TWRP and CWM. In the past I was not possible to switch, and use the backups from one to the other. Now that's changed and they are basically compatible making the choice between them just a personal preference. Let me know if the Galaxy Tool Hidden menu app helped ?
[XDA Assist] XDA Visitor:
I have Samsung Galaxy Mega Duos(GT-I9152) with Bootloop problem,so I firmware with official one but it's still restarting, reach to Samsung logo and restart,furthermore I wiped cash,factory reset,devlik and it's the same result restart.....Bootloop.
[XDA Assist] It_ler:
Ok, usually you have to completely power off the device. Either long-press/hold the Power key till the display is (ans stays) black, or remove the battery for a few seconds.

If it does not help, please post your question in the Samsung Galaxy Mega > Galaxy Mega Q&A, Help & Troubleshooting > Help thread.

It's originally not exactly for your device, but as it's very similar, you may get help there too.
[T-Mobile LG G2] inpherknow:
After lunch, I was greeted with the following message on my G2.

I'm not in a position to where I can run this now. Has anyone else gotten this? Is it Lollipop?
[T-Mobile LG G2] MicroMod777:
Nope. Its D80120e-D80120g_update.
[T-Mobile LG G2] Deleted member 4738840:
Is there any good updates, or is it just optimizing for T-mobile?
[T-Mobile LG G2] nalanotae:
I semi bricked my d 801 had to flash the 20e kdz saw an update available and thought the same thing, is this lollipop? Took the ota realized it wasnt, try to reroot using towel root and install recovery with autorec and it was a no go had to use lg flash tool again to go back 20e just to root
[T-Mobile LG G2] nalanotae:
Now I cannot get my phone to update to 20g it said 20e is up to date. Why?
[T-Mobile LG G2] mdowns989:
So if you're STOCK but rooted with custom recovery and you take this update is it going to soft brick the device or will it just unroot you and be okay?
[T-Mobile LG G2] cangri87:
It will soft brick if you do OTA via phone with 3rd party recovery, it will unroot you if you do it via the pc lg suite

Software, from my past experiences.
[T-Mobile LG G2] nyt:
If you bricked your phone trying to apply this, the fix is simple if you have TWRP or some recovery that gives you adb shell access.

Just run the following. It will clear out the OTA.

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
[T-Mobile LG G2] demonicturd:
Please help

Hey, im definetly new to this but a couple months ago my friend convinced me to root my phone. I used towelroot and I got rooted.

I also got this update and I thought it would be fine to get it. It messed my root up. I factory reset my phone because I couldnt connect to a seperate gmail and play store

I really need help but I really dont know anything about TWRP and recovery stuff , all I had was towelroot, root checker, super su, and freedom. My friend obviously didnt tell me to get anything else.

I cant connect my gmail on startup or anything else, I tried to change a etc/hosts file but I need root which I dont have. If anyone can help please do. I dont have data and my phone is locked other than I can get on wifi and I WAS able to download apps from play store... :crying::crying::crying::crying:
[T-Mobile LG G2] diamond12:
I don't have a link but you can Google stump root, it worked for me to re-root.
[T-Mobile LG G2] m.r.ekcah:
Here's the info about the update

https://support.t-mobile.com/docs/DOC-7591
[T-Mobile LG G2] MicroMod777:
Any news?
[T-Mobile LG G2] 4GivenByChrist:
It seems Lollipop should be close, someone posted a link to the 5.0.2 open source from LG in another thread.

http://xdaforums.com/showthread.php?p=59384781
[T-Mobile LG G2] yehison:
Coming soon official lollipop..

https://llaverotecnologico.wordpress.com/2015/03/19/lollipop-se-aproxima-a-lg-g2/
[T-Mobile LG G2] caaznkid:
bout timeeeee :fingers-crossed:
[Samsung Gear S] squeakywipers:
If stand-alone WhatsApp is available for the Gear S, I'd buy this phone/watch in a heartbeat. I've been a huge phablet fan, and the Gear S would be a great for the occasional night out and leaving my huge phone home. As an avid runner, the Gear S functionalities are amazing.

Been pondering using the Gear S for communication via phone/text/WhatsApp exclusively, and switching to a small tablet with LTE for daily use.

Any thoughts?
[Samsung Gear S] megatherian:
No whatsapp for Gear s that I am aware of yet - or any other real messaging app (someone correct me if I'm wrong).

I telecommute so rarely leave the house except for errands and I hate bringing my phone with me. I don't need all the fancy stuff for when I'm at the grocery store and when I do need internet etc I'm usually at home. The Gear S is a perfect phone replacement for me.

If I was in a different situation where I was away from home and internet more often I think I'd want either a more traditional phone or tablet as well. The Gear S is a great device and I enjoy using it for internet and such when for example I'm sitting in a waiting room but to me, it's still a companion device that can occasionally act as a standalone device.

Of course your needs and mileage may vary but that's my 2 cents.
[Samsung Gear S] willmir:
"Notifications for Gear S"

I just downloaded "Notifications for Gear S" from the Samsung App store. It works great to respond Whatsapp messages. I believe it also works with other messengers as well.
[Samsung Gear S] tornado6:
paid app?
[Samsung Gear S] bennie joe:
I don't believe What'sApp is supported right now...
[Samsung Gear S] squeakywipers:
I have a feeling that we are only a couple of months away from a 3G enabled smart watch from a competitor (Huawei, Asus, etc) that will run android wear... And perhaps even be cheaper than the Gear S and offer more apps. Therefore, I think I'm gonna hold out buying one for a few months. Luv the fitness features of the Gear S, but if it's a choice between more apps like WhatsApp over a heart rate monitor, the former would win.... It's nice to know my heart rate, but hey, as long as it's beating, right.....
[Samsung Gear S] joytest:
It would likely be a forked Android Wear, as i think I read somewhere that Google does not intend for Wear to be call-capable on its own.

If so, you'd run into the same issue with Samsung, needing a specific manufacturer's phone to pair with the smartwatch.

Well, who knows....
[Samsung Gear S] sbrownla:
Android Wear is even more dependent upon a connected phone than the Gear S. It can run separate apps but ... I wouldn't give it too much hope.

LG is rumored to be working on a 3G watch so you never know ... but just have to wait there will always be something following what's already out here and since this is Samsung's 6th watch they probably have a better handle on how to get things up and running than their conpetition.
[PDA2, XDA IIi, 2020i General] manoual:
Hello all...This may be my first post but i have beed watching the forum for quite a long time!You are doing a great work around here!

I need a big favor from anyone that can help!Does anyone have the original SPV m1500 rom provided by orange and can upload it somewhere for me to download?Or can anyone back up his ROM from a m1500 and upload it somewhere?

And i have question as well and i would be grateful if you could answer this one!

If you haven't CID unlocked your phone and somehow managed to upgrade the ROM with a different make's one (i have one from Qtek 2020i at the moment) will it be blocked by the network or is a matter that the person that i bought it from (over ebay) reported it as lost/stolen?Currently everything works fine apart from the phone bit!It says no service and can't detect any network!(it just says ''unable to read setting from the network.Try viewing settings later or disconnect data connection and try again'').

Any help would be greatly appreciated
[PDA2, XDA IIi, 2020i General] manoual:
sorry double post!server had problems!can a moderator please delete one of them/?
[PDA2, XDA IIi, 2020i General] manoual:
Any help pls!??
[PDA2, XDA IIi, 2020i General] clustered:
Hi,

SPV M1500 same as O2 Xda IIi / Dopod 699 / i-Mate PDA2 / Qtek 2020i and known as HTC Alpine. You can upgrade using any ROM that build for HTC Alpine.

Please check at here about all in one sim unlock tool by itsme

http://xdaforums.com/showthread.php?t=240784

Thanks ;)
[PDA2, XDA IIi, 2020i General] manoual:
Thanx clustered for the reply!

I have already used that thread to upgrade my firmware but i am just asking if i anyone has the original SPV m1500 orange rom available?

The thing is i have done the upgrade without CID unlocking the phone!Everything went ok but the only problem is that now the phone in the signal bar has an exclamation mark and says no service!So i was just wondering if it is the upgrade that ''blocked'' the phone bit of the M1500 or is it something else!

Thanks again
[PDA2, XDA IIi, 2020i General] manoual:
after a lot of search i found in a forum someone stating that :

''RIM check the ROM version and RADIO version before they allow you to connect to the relay. If it's not an approved mix, your device IMEI will be BARRED from the relay.''

is that possible and do you think that's why my phone gives the no service message?

Could anyone suggest any solutions to this?
[PDA2, XDA IIi, 2020i General] manoual:
anyone can help??