yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] npaisnel:
Yes, I am too interested in any updates to this other than the Kingo root route
[General Questions and Answers] pro-handler:
I rooted my brother 's fone wid kingo root and it worked buh i can't install the framework of xposed framework.....any help please??
[General Questions and Answers] jabba dan:
does any one know if the rom on this site works for Huawei Y330 phone lollipop-rom if it does could you email it to me , am not allow to dowload it in my country. jabbarandall@gmail
[General Questions and Answers] beraka1995:
How to root your huawei ascend y330

Hi, I have bought this done two day ago and yesterday, I was searching also how to root this device. So to root your done,

1. Download 4shared app on Google play

2. Open and search for: ROOT MASTER+SUPER SU+ ROOT CHECKER. ZIP

It is a zip file,

Size: 3.27Mb.

Go to your file manager in download and open zip then install.

After install, you open Root master. It is in Chinese but you will see where it is written root.

Caution: do not touch the red bouton.
[General Questions and Answers] ivanovish28:
Ive got dat problem also
[General Questions and Answers] Berties123:
bought one of these, y330 -u01. Tried kingo, it installs su, but it cannot install binary, so it's not fully rooted. cpu-z says it's rooted, but cannot do any SU things like adaway
[General Questions and Answers] dragnan:
I so hate the Huawei styled UI - both icons and modified popup styling.

So I've been working on creating a ROM based on the original one combined with a few of my own modifications as well as some mods from Speedys material mod - and now, I think it is ready for sharing with you guys.

It is rooted and lots of Huawei stuff is gone. Finally, I actually kinda like the phone now.

To install it, first get CWM installed. Then simply copy zip to an SD Card and install it. Please let me know what you think about it - and feel free to push the Thanks! button.

Enjoy.

https://drive.google.com/open?id=0B6N9Q-rIDPiqYld5eDJTTWdJWDQ

After installation and first start, it will notify you to update the SU Binary. Select the TWRP/CWM way to install. The standard way will fail.
[General Questions and Answers] Tekiruki:
Send some screenshots
[General Questions and Answers] Deleted member 5868905:
For what submodel is this? There are Huawei Y330-u01 u05 u07 u11, idk if there is u05 but flashing on diffrent device will make it bootloop
[General Questions and Answers] mauriciognr:
This won't help OP, but it might help someone else. I made the following videos about how to install CWM , and root and Sim unlock a Huawei Y330.

[YOUTUBE]x7_n5P7yBaQ[/YOUTUBE]

[YOUTUBE]GiAW9DU2-X4[/YOUTUBE]

PS: They are in spanish.
[General Questions and Answers] Frankennoob:
Anyway you could post written instructions in english please
[HTC Rezound] bunchies:
Default TCP Congestion Control - Veno

Default CPU Governor - Interactive

Default I/O Scheduler - Row

Changelog:

Kitten-Kernel v3.0: [MENTION=3419683]Snuzzo[/MENTION] for both these

Reduce WiFi Wakelock

zRam Swap

Kitten-Kernel v2.9:

Revert My Reverts For Display Stuff

Remove CONFIG_SCHED_AUTOGROUP From Last Version

Adapt memutils Optimizations From msm8960pro (Thanks [MENTION=3419683]Snuzzo[/MENTION])

Kitten-Kernel v2.8:

Revert "Update Display Driver" From v2.5 (Will probably bring this back but needs more testing)

Add CONFIG_SCHED_AUTOGROUP (Has been known to improve performance on linux PC's)

Cleanup/Fix Some Stuff

Fix Flashing Support For S-ON Users In Both New/Old Recoverys

Kitten-Kernel v2.6:

Add Support For Non-Powered OTG Cables

Kitten-Kernel v2.5:

Update Display Driver

Cleanup Unused Code

Add GOV Iulzactive

Kitten-Kernel v2.4:

Update USB drivers from GoogleSource

Update LowMemorryKiller to the new Version

Add Random number generator to USB driver for more speed

Minor cleanup for old-code/bugs

Kitten-Kernel v2.0:

Update ZIP Naming/Push 2.0

Add Zen I/O Sched

Update SIO I/O Sched

Update ROW I/O Sched

Misc I/O Sched Updates

Update GOV Interactive

Update GOV Ondemand

Update SELinux

Update Binder

OTG (Powered Cable)

Enable TCP Congestion Selecting

Add TCP Algorithm BIC

Add TCP Algorithm HYBLA

Add TCP Algorithm HSTCP

Add TCP Algorithm HTCP

Add TCP Algorithm ILLINOIS

Add TCP Algorithm LP

Add TCP Algorithm SCALABLE

Add TCP Algorithm VEGAS

Add TCP Algorithm VENO

Add TCP Algorithm WESTWOOD

Add TCP Algorithm YEAH

Add TCP Algorithm VENO

Kitten-Kernel v1.0 (Re-uploaded):

Fix WiiMote connection

Remap the WiiMote driver buttons to force the WiiMote to be held in landscape mode by default

Mounting Storage With OTG:

Use either an OTG app or a file explorer, USB storage devices will be mounted to /usbdisk

Im trying to get this merged to our recovery also so we can backup encrypted nandroids to a flash drive :angel:
[HTC Rezound] bunchies:
Let me know if you have any issues with this kernel

there is another project im working on so new features may not flood in right away
[HTC Rezound] bacon612:
Flashed this to my rezound running cm11. Booted fine and seems to be running great so far. Will report back with any findings.

What specifics did you change to get wiimote working? Is it to say that I can use wiimote apps from the play store now? Does this fix the Bluetooth issue that Google changed after 4.1.2? I used to love playing SNES ROMs on my tablet with my wiimote. Perhaps the best companion on a flight ever.

Thank for your work on this Devs.
[HTC Rezound] knoc:
can i flash this without having to flash a boot.img afterwards ? thanks in advance
[HTC Rezound] bunchies:
With the WiiMote i had to add back the driver that was missing, its also not available for 3.0 kernels by default.

now in my testing its not working in 4.4.3, if the LED's keep flashing than its not completely connected & i will get this working again

but when it is working there is no need for extra WiiMote apps from the playstore to connect or button map because its all baked into the driver thats inside the kernel :good:

Edit: just fixed it :D
[HTC Rezound] bunchies:
You should be able to, i haven't tested this myself since i am not s-on but the scripts used support s-on detection

it will than make a flashable zip that is compatible with the bootloader than reboot to bootloader and flash it for you

if you test this let me know, i remember this script worked fine for older kernels but i currently need feedback on it
[HTC Rezound] bunchies:
okay, re-uploaded the kernel check the changelog in post 2 :good: just wiimote fixes
[HTC Rezound] knoc:
When flashed it restarted to bootloader I flashed my IMG and all is well

Ty
[HTC Rezound] Snuzzo:
Heya kiddo! Please add a mention in credits to [MENTION=2907283]con247[/MENTION] for original scripting that was brought into the kernel build scripts. TIA! Have fun. :)
[HTC Rezound] bunchies:
Thanks snuzzo
[HTC Rezound] Snuzzo:
Anytime! Also got a little extra mod you might be interested in. Its regards to the advanced TCP control algorithms.

https://github.com/IllusionRom/andr...mmit/ff33333403d82b3105897e7331ac11618489af8e

If you don't use this and attempt to run say Westwood as default, kernel will kick it back to Cubic.
[HTC Rezound] bunchies:
Nice, thanks again! :thumbup:

Will definitely try this, was holding off the next version of my kernel since REV and I joined a project regarding our kernel getting out of legacy and I didn't want to spend a lot of time debasing this kernel if the project was successful but I think I'm just going to start adding things again :p
[HTC Rezound] Snuzzo:
Understood. I was working on DT2W right before picking up the G2, had lost the commits thinking they were pushed to remote and deleted local source. I know fail moment right?
[HTC Rezound] bunchies:
Haha, I wouldn't know what to do if that happened to me.

And I would like to get DT2W working but I'm unsure if I wanna do all that just to leave this phone for the g3

I still plan to dev for this phone after I leave but idk :p
[HTC Rezound] bunchies:
Just want to make a quick post

Big Thanks to [MENTION=3419683]Snuzzo[/MENTION] for letting me use his server for my builds :good:

edited the credits for this also
[HTC Rezound] bunchies:
New version up!

More to come soon :D
[HTC Rezound] bunchies:
Version 2.4 Out! :good:

Wanted to push out an update before i left for vacation today :angel:
[HTC Rezound] md303:
Thanks, enjoy your vacation!

One tiny request, very low priority (I'm still on CM10.1) - can you add LulzActive governor? I have had great results with running Core0 on LulzActive and Core1 on Badass. Not sure if Lulz is even relevant any more, but I do like it. :fingers-crossed:
[HTC Rezound] bunchies:
Yeup :thumbup:

Anymore requests I can add

Smartass govs don't like us :p
[HTC Rezound] md303:
:victory: You rock!
[HTC Rezound] SigLover21:
Will this work with CM11 4.4.4 the newest one? I just wanted to check before I nuke my phone. Also I was hoping to fine a governor with Interactivex. So if that a possibility for future builds please keep it in mind.

Thank you:laugh:
[HTC Rezound] bunchies:
Yes, and that will be added :thumbup:

Working on another project that is taking up a lot of my time but I should have a build out by the 13 or 15 which will include requests and more
[HTC Rezound] bunchies:
well that was alot of work lol

[MENTION=2800910]md303[/MENTION]

LulzActive was added

[MENTION=4151304]SigLover21[/MENTION]

Interactivex was added

i know the link isnt up right now, just want to do a little testing

EDIT: ran into some issues with both the Govs, everything else is fine. i want to get a build out today with or without them but they will be on the top of my list

ill see if i can fix them today though
[HTC Rezound] Snuzzo:
[MENTION=5035862]bunchies[/MENTION] [MENTION=4151304]SigLover21[/MENTION]

You won't want interactivex. It doesnt work as good on this device.
[HTC Rezound] bunchies:
Thanks, I knew smartass had some bad experiences but didn't know interactivex was also the case
[HTC Rezound] bunchies:
And its up! :D Check the changelog

[MENTION=4151304]SigLover21[/MENTION]

Sorry i couldnt get Interactivex working, snuzzo did point me to an earlier version that might work but we are unsure right now

So hopfully it might be added one day
[HTC Rezound] bunchies:
New update

Please read this post

http://xdaforums.com/showpost.php?p=53443459&postcount=2

Rally-up a mob :o the petition has started
[HTC Rezound] el Filou:
Just to make sure: 'non-powered' means you got the Rezound to actually power the USB device itself?? :fingers-crossed: (I remember SebastianFM saying that the HTC 8x60 boards couldn't send power to USB :confused:)

Or it just means the device must have its own discrete power source instead of getting power from the cable?
[HTC Rezound] bunchies:
Yes the device can now send power to otg
[HTC Rezound] Snuzzo:
I have merge rights. How far tested was this?
[HTC Rezound] bunchies:
[MENTION=3419683]Snuzzo[/MENTION]

Since the day I merged it to my tree its been in my LS builds, so like 2 months I think

But my ROM is compiled with stock vigor github kernel and the fstab has no issues with it

If you read through it, Its just a folder being made and being targeted as a mount point for whenever a OTG device gets found from the fstab line

I don't see any negative things about it, the rest if the team has seen it since I posted it in hangouts
[HTC Rezound] Snuzzo:
Merged. :)
[HTC Rezound] bunchies:
Thanks :thumbup:

What's next to fix lol
[HTC Rezound] Snuzzo:
Feature list;

Double tap to wake

Functionality list;

Wifi power draw.
[HTC Rezound] bunchies:
I have plans for double tap

What needs to be done with WiFi?
[HTC Rezound] Snuzzo:
Looking to reduce the power draw for wifi just a little.
[HTC Rezound] Sultanxda:
Next time you may want to use Git's cherry-pick feature. Add .patch to the end of the commit URL (https://github.com/sultanxda/sultan...8a530c12458d939f8c3f7fdd2ff4277645fed5e.patch), right-click and choose save as, copy the patch file to the root of your kernel directory, open a terminal, cd to the root of your kernel directory, and run git am name.patch. This will retain proper authorship & commit date on GitHub and you won't have to manually edit any files with the changes.

Also, johnnyslt was not involved in the creation of that patch.
[HTC Rezound] bunchies:
Okay, thankyou :good: i dont know exactly every git command just yet
[HTC Rezound] Sultanxda:
Neither do I :p My mind was blown when I learned about cherry-picking haha. Git is magical.

Some devs on XDA might go into super saiyan rage mode if they aren't credited properly (I remember getting an angry PM a year ago from one of them), so Git's cherry-pick feature is a nice way to prevent something like that from happening.
[HTC Rezound] bacon612:
Hey I'm running chucks latest cm11 with your 2.6 build. Seemed to have lost "AC" charging with my Motorola 1amp car charger. Is this normal? It used to work.
[HTC Rezound] bunchies:
See if it works well on the included ROM kernel, maybe even test it on v2.5

In the meantime I'll be testing the voltage input and see if it can be upped a bit
[HTC Rezound] md303:
I'm not having any luck with this kernel. I just wiped my phone today and loaded LS v3.2 (latest build), let it boot and settle in, then rebooted and flashed the kernel. Upon bootup I get infinite force close messages that com.android.systemui has crashed. It just does this over and over every time I dismiss the message. Rebooting doesn't help, and if I turn the screen off, it will not turn back on again and I have to do an ADB REBOOT.

I've repeated this problem on the 3 most recent LiquidSmooth releases in the OP with identical results. WTF? I've been modding HTC phones since the Incredible and have never had this problem before!
[HTC Rezound] bacon612:
I reflashed the ROM and actually had the same result. It seems it may not be your kernel after all. Still sucks tho. I double checked and the car charger drives 950mA. That should be enough to charge the red quickly, no? OEM charger is 1A I think. Will continue testing. I'll try your 2.5 too.
[HTC Rezound] bunchies:
950mA should be enough

USB 2.0 does 500 mA

USB 3.0 does 900 mA

Default HTC Charger that comes with the phone does 1A

ive seen what ur talking about though, if i use my phone while its charging i can literally watch it lose battery. and with how much heat this phone produces i dont really think touching the values for charging would be safe

I have not touched any values for the charging port, only enabled OTG function on it
[HTC Rezound] bunchies:
Wow, Sorry for your issues

And everything is fine up until flashing kernel?

Both ROM/Gapps and maybe a few reboots

I probably don't need to ask this but your wiping everything besides SDcards correct?
[HTC Rezound] bunchies:
Twrp users

Get the latest twrp, some fixes and otg support http://xdaforums.com/showthread.php?p=31940448&nocache=1
[HTC Rezound] md303:
Yea, I'm well-versed in all of this, very strange that I can't get it to work on a 100% clean wipe & flash (except EMMC/SD). Without trying a kernel flash, I've gotten the 3 most recent Liquid Smooths to work fine on every flashing attempt.

I wonder if there's something about AmonRa Recovery that isn't flashing the kernel properly. I don't like TWRP and haven't used CWM for ages but maybe I should try TWRP again.
[HTC Rezound] bunchies:
that should be an issue, AmonRa is so outdated.

TWRP and CWM were updated to support KitKat :good: as a past AmonRa user i did switch to twrp and liked it

i personally dont like CWM but at the end of the day its just a recovery
[HTC Rezound] md303:
Ahhhhh, now for the fun part. Gotta flash TWRP, back up my LiquidSmooth image, flash AmonRa to restore my perfect CM10 build, reflash TWRP and take a new backup of CM10, then re-flash LiquidSmooth.

EDIT: Holy crap, TWRP is way better than the last time I tried it (long before Touch existed)! byebye AmonRa

EDIT: Done converting my AmonRa backups to TWRP. TWRP is much faster than AmonRa too, glad I made the switch! Next step (tomorrow) - try flashing kernel again.
[HTC Rezound] md303:
Well how about that! Kernel flash problem was because of AmonRa. I flashed the kernel with TWRP and all is well!
[HTC Rezound] JPHoller:
TWRP S-ON Flash

Hi,

I am S-On and was wondering how to flash this kernel. I flash in TWRP, it takes me to fastboot, then just sits there?
[HTC Rezound] bunchies:
It'll make a flashable bootloader zip, so when it fastboot mode switch it to bootloader mode

Edit: I have another build coming soon, so check back in a bit for that also
[HTC Rezound] knoc:
Not tonight?
[HTC Rezound] bunchies:
Its 10:40pm I can probably just upload it now

While I was testing new stuff a really bad bug appeared but it's related to the previous release so I just want some extra testing in

EDIT: its up
[HTC Rezound] JPHoller:
I downloaded the new build, placed on root of internal storage. cleared cache and dalvik cache in TWRP. When i install zip, it will create the PH img and reboot into hboot, but will not load. Keeps stating that it is loading but no .img found. This could be something i am doing wrong on my end. Thank you for all of the help so far.
[HTC Rezound] bunchies:
What version of twrp?, also try deleting any existing PH zip from your sdcard and see if it helps
[HTC Rezound] JPHoller:
Im running 2.7.1.1. Just tried again after removing previous PH zips. Still no go. Is there another way to flash this? Possibly fastboot?
[HTC Rezound] bunchies:
If you want to you can try, the PH zip should contain a boot.img than you can flash through fastboot
[HTC Rezound] knoc:
Flashed 2.7 wiped both cache and davlik like usual and it restarted me to fastboot. Never had that happened before. Loaded up recovery wiped both caches again and restarted system. Booted up but idk of im running 2.7 or the kernel L's comes with it says

4.0.101ck-gc2a2014 bunchies@bunchies G1-geuerilla #1 20th Friday 00:35:39 2014
[HTC Rezound] bunchies:
So its not flashing correctly for S-ON users, 3.0.101ck-gc2a2014 is stock kernel

should say the following in about phone if it flashed:

3.0.101-Kitten-Kernel-v2.7+

bunchies@bunchies G1-geuerilla #1

Wed Jul 23 20:51:05 PDT 2014

i can rebuild but i need a tester before full upload again
[HTC Rezound] bunchies:
If your using this kernel, please delete 2.7 zips if you have one laying around.

ill be releasing 2.8 very soon
[HTC Rezound] undeadking:
Love that non powered OTG works!!! Great kernel Bunchies!!!
[HTC Rezound] knoc:
I'd test but I work 1-10 tonight. When I get home hopefully the 2.8 build is out and I'll flash and give u my results ty in advance
[HTC Rezound] bunchies:
2.8 is out :thumbup:
[HTC Rezound] knoc:
same results 8^(
[HTC Rezound] bunchies:
how many times have you flashed the kernel with the newest twrp 2.7.1.1?
[HTC Rezound] knoc:
Not positive

---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------

2.6 worked with it I'm pretty sure
[HTC Rezound] bunchies:
Can you try the last working twrp for you? version 2.7 and 2.8 is the only ones reporting issues and it started happening when the newest twrp was released

The s-on scripts haven't been touched but the things they detect may have moved due to new twrp (I'm guessing on that)
[HTC Rezound] knoc:
I will some other time too busy tonight 8(
[HTC Rezound] knoc:
Twrp 2.7.1.0 or whatever the older release flashes kernel 2.8 no problems
[HTC Rezound] Snuzzo:
[MENTION=5035862]bunchies[/MENTION]

Just flashed twrp 2.7.1.1 and will be looking into the AnyKernel s on installer issues soon. Expect a pull request.
[HTC Rezound] bunchies:
Awesome :thumbup:
[HTC Rezound] Snuzzo:
OK found the issue in CopytoSD.sh

instead of

#!/sbin/sh
#
#
# Kludgy hack to help with kernels
#
cp /tmp/PH98IMG.zip /sdcard/PH98IMG.zip
exit 0

Copy and paste the following creating a modified/new CopytoSD.sh

#!/sbin/sh
#
#
# Kludgy hack to help with kernels
#
cp /tmp/PH98IMG.zip /external_sd/PH98IMG.zip
exit 0
[HTC Rezound] bunchies:
Thanks, I'll merge and get a build out :D
[HTC Rezound] Snuzzo:
If that doesn't work I'll look deeper for now that SHOULD do the trick. First to confirm; anyone s on and using 2.7.1.1 try to flash 2.8 and it will put the ph98img on your internal sd.
[HTC Rezound] bunchies:
[MENTION=3419683]Snuzzo[/MENTION]

If it's just the sdcard being renamed and us retargeting it than wouldn't that break previous versions of recovery

Could we in the future maybe be able to mount the actual partition for the external sdcard rather than finding "/external_sd"
[HTC Rezound] bunchies:
Re-uploaded 2.8, S-ON users please report back if it works with the latest TWRP :good:
[HTC Rezound] Snuzzo:
Behoove users to update their recoveries If you wish to add compatibility well here let me get you something ;)

#!/sbin/sh
if [ -d /external_sdcard ]; then
cp /tmp/PH98IMG.zip /external_sdcard/PH98IMG.zip
else
cp /tmp/PH98IMG.zip /sdcard/PH98IMG.zip
fi
exit 0
[HTC Rezound] bunchies:
That's the easy way but if we wanted to later we could add support :p

Now I was also thinking of using a set of if/else statements for both partitions but the "/sdcard" still exists in the recovery fstab for internal sdcard

https://github.com/Bunchies101/devi...02a08aff91667030fdb66/recovery/etc/twrp.fstab

I'm starting to come up with ideas on how we could get it to work but I'm not to concerned about it today
[HTC Rezound] Snuzzo:
Yes but see it will do a check for external_sd dir first, which doesn't exist in the older recoveries (sdcard & emmc does). And hboot won't use internal if users run without an external sdcard, which if you're s on you will need one for those functions. So now it falls on the user to provide the hardware needed.
[HTC Rezound] bunchies:
Oh duh!! Damn I need to exercise my brain lol
[HTC Rezound] Snuzzo:
LOL

I will cater to the s-on guys because I've seen way too many bricks with user error+s off. Sorry, I beleive s-on is there for a reason, s-off is for the dev guys & those who get alot more in-depth. It's their to prevent any hardware damage, soft bricks are easier to recover.
[HTC Rezound] bunchies:
Yeup, seems like all the user's recommended s-off to eachother :p so there are only a few s-on ppl left, don't want to force them into possible brick trying to s-off

Although a lot of people upgraded already so the rez community is small

I'm gunna go brush up on my python a bit or play around with current/finished projects since it's been like 2 months, When you get confused about a if/else/elif statement something's wrong. I do think seeing both names in fstab is what made the confusion start though lol
[HTC Rezound] Snuzzo:
I've employed that fix for "external_sd" a long time ago (Auto S-On branch in Snuzzo/device_htc_vigor). That installer employs absolute sha1 checksum comparisons between both ramdisk and zImage. Which i'm looking to update IllusionRom soon.
[HTC Rezound] ClockerXP:
Thank you for your work on this Kernel!

Are there any known improvements to battery life using this rom on CM11 Hybrid ROMs such as (ROM)(4.4.4)(UNOFFICIAL)CyanogenMod 11.0(08-01-14)(GPL)(HYBRID) ?

What's the best way to backup my existing (stock CM11) kernel that came with the ROM if I want to give this one a spin?

What's the most notable improvements from stock when switching to this Kernel?

Thanks,

ClockerXP
[HTC Rezound] Snuzzo:
4 ways

1

Using a PC

adb shell

dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img

Current boot.img will be placed on your storage. Do not mistype that command.

2

Using TWRP create a backup of your current rom. Only restore boot.img. Use Dumlock if s-on.

3

Using CWM/Philz create a nandroid backup. Boot.img will be created.

4

Using your custom rom's zip. boot.img will be in the root of the zip file.
[HTC Rezound] bunchies:
I'm unsure if backing up a boot.img in recovery is still a thing on the rez but if you backup your boot.img you can restore later if you want stock kernel back

Or the second option to get stock Kernel back would be to extract the boot.img from the ROM zip and flash it through fastboot

The rezound doesn't have the most amazing battery but the stock kernel doesn't offer many governors to play with, there are some tweaks in this kernel that may help out that are not governor related but user usage may vary

More features and smoothnes vs stock Kernel, none that should effect battery