Yank555.lu Android Stuff

Working good here! Yank555 any chance of adding device ID N900W8, hltecan to the update.script? I apologize but I had to remove device check to install it on my N900W8. working great so far TY

turilo wrote:Working good here! Yank555 any chance of adding device ID N900W8, hltecan to the update.script? I apologize but I had to remove device check to install it on my N900W8. working great so far TY

Well if it's working fine as is, I don't know all the models that are "identical" hardware wise.

You you check in the recovery what the correct device ID is ? Should be something like "hlte...", n9005 is a hlte, n900T is a hltetmo etc.

JP.

yank555 wrote:

turilo wrote:Working good here! Yank555 any chance of adding device ID N900W8, hltecan to the update.script? I apologize but I had to remove device check to install it on my N900W8. working great so far TY

Well if it's working fine as is, I don't know all the models that are "identical" hardware wise.

You you check in the recovery what the correct device ID is ? Should be something like "hlte...", n9005 is a hlte, n900T is a hltetmo etc.

JP.

The device id is hltecan, which is for the N900W8 note 3

Hmm Seemed to get a device assert error 7 when flashing this, Checked build prop and its listed as "Hltexx"

Am I missing something

* Love the aroma installer though, so many settings

Gonna edit the build prob back to the should of been default "Hlte" hopefully this clears the error.

Edit** Still same error its coming back saying my device is Hltetmo :S

I want to edit the updater script but it;ll bug me thinking my device thinks its a tmobile variant !!

FIXED: Changed to Teamwin Recovery and it flashed without an issue Success !!

Hi @Yank555, thanks a lot for your work!

Could you please update the installer so that it works on hltexx as well? I have edited the device assert in the updater-script as follows:

Code: Select all

assert(getprop("ro.product.device") == "hlte" || getprop("ro.product.device") == "hltetmo" || getprop("ro.product.device") == "hltexx");

and it installed fine.

By the way, temasek was able to update the kernel sources to 3.4.77 (he admitted it wasn't very easy) - you should be able to merge his update commits from here:
https://github.com/temasek/android_kern ... mmits/temp

Keep up the good work!
Cheers Pete

piit79 wrote:Hi @Yank555, thanks a lot for your work!

Could you please update the installer so that it works on hltexx as well? I have edited the device assert in the updater-script as follows:

Code: Select all

assert(getprop("ro.product.device") == "hlte" || getprop("ro.product.device") == "hltetmo" || getprop("ro.product.device") == "hltexx");

and it installed fine.

Damn, which recovery is using this wrong devi ID !? hltexx is no device

This needs to be fixed on the recovery side...

piit79 wrote:By the way, temasek was able to update the kernel sources to 3.4.77 (he admitted it wasn't very easy) - you should be able to merge his update commits from here:
https://github.com/temasek/android_kern ... mmits/temp

Keep up the good work!
Cheers Pete

Not really convinced that's worth the effort tbh...

I rather spend my time on more productive stuff

JP.

Send from my 'proudly eFused' Note 3 (n9005) running Yank555.lu v0.7 kernel.

turilo wrote:The device id is hltecan, which is for the N900W8 note 3

I've updated my script, will be in by default in the next version.

JP.

BTW, it seems Touchwake is not working at all, I suppose it will need some reworking...

Also, do change the governor to ONDEMAND, the default will drain the battery, don't understand why CM changed the default ?!

I didn't check that, sorry. Next update will be "more" checked, this one was a fast shot

JP.

yank555 wrote:Damn, which recovery is using this wrong devi ID !? hltexx is no device

This needs to be fixed on the recovery side...

Are you sure about that? Official CM11 nightlies use

Code: Select all

ro.product.name=hltexx
ro.product.device=hltexx

And this is the assert in the CM11 installer:

Code: Select all

assert(getprop("ro.product.device") == "hltexx" || getprop("ro.build.product") == "hltexx" || abort("This package is for \"hltexx\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

I had the opposite problem when trying to install CM11 using TWRP 2.6.3.7 - it was saying this is a "hlte". So I switched to official CWM 6.0.4.6 which uses

Code: Select all

recovery$ getprop
...
[ro.product.device]: [hltexx]
[ro.product.name]: [hltexx]
...


So I expect your kernel would flash in TWRP - but CM11 doesn't.

yank555 wrote:Not really convinced that's worth the effort tbh...

I rather spend my time on more productive stuff

Completely understand that I just thought that pulling in temasek's commits would be fairly easy. Maybe when you won't have anything else to do...

Cheers Pete

Well, let me put it this way ... who gets to name a kid ? The parents, right ?

The parents are Samsung :

Exerp of original build.prop of stock TW ROM (MI7) :

ro.product.model=SM-N9005
ro.product.brand=samsung
ro.product.name=hltexx
ro.product.device=hlte
ro.product.board=MSM8974
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB

I don't get it why CM now is coming up with a new fancy name !?!

JP.